From exim@www1.ietf.org  Tue Jul  1 15:11:29 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 PAA12433
	for <imrg-archive@odin.ietf.org>; Tue, 1 Jul 2003 15:11:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XQWt-0002Rl-7L
	for imrg-archive@odin.ietf.org; Tue, 01 Jul 2003 15:11:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h61JB3r8009400
	for imrg-archive@odin.ietf.org; Tue, 1 Jul 2003 15:11:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XQWt-0002RH-13
	for imrg-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 15:11: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 PAA12322
	for <imrg-web-archive@ietf.org>; Tue, 1 Jul 2003 15:10:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XQWm-0007Dw-00
	for imrg-web-archive@ietf.org; Tue, 01 Jul 2003 15:10:56 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XQWl-0007Dp-00
	for imrg-web-archive@ietf.org; Tue, 01 Jul 2003 15:10:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XQVx-0002J1-Gg; Tue, 01 Jul 2003 15:10:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XQVc-00029T-BS
	for imrg@optimus.ietf.org; Tue, 01 Jul 2003 15:09:54 -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 OAA09747
	for <imrg@ietf.org>; Tue, 1 Jul 2003 14:14:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XPeA-0006nC-00
	for imrg@ietf.org; Tue, 01 Jul 2003 14:14:30 -0400
Received: from tokyo.ccrle.nec.de ([195.37.70.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XPe9-0006mq-00
	for imrg@ietf.org; Tue, 01 Jul 2003 14:14:29 -0400
Received: from venus.office (venus.office [10.1.1.11])
	by tokyo.ccrle.nec.de (8.12.9/8.12.8) with ESMTP id h61IDoVI007926;
	Tue, 1 Jul 2003 20:13:53 +0200 (CEST)
Received: from ccrle.nec.de (molina.office [10.1.1.126])
	by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP
	id 8DEFAAB912; Tue,  1 Jul 2003 19:57:26 +0200 (CEST)
Message-ID: <3F01CF5B.8010104@ccrle.nec.de>
Date: Tue, 01 Jul 2003 20:13:47 +0200
From: Maurizio Molina <molina@ccrle.nec.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mallman@grc.nasa.gov
Cc: imrg@ietf.org
Subject: Re: [IMRG] Flow sampling (or selection)
References: <20030530132952.C71D66B17A@lawyers.ir.bbn.com>
Content-Type: multipart/alternative;
 boundary="------------050805060509070506030408"
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>


--------------050805060509070506030408
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Mark Allman wrote:

>>As far as I know IPFIX deals with reporting per flow information,
>>PSAMP with sampling and reporting per packet information, selected
>>with some criteria.  Has there in any of these groups (or
>>elsewhere) been any discussion about FLOW sampling? I've seen
>>papers about it, e.g.
>>
>>http://www.research.att.com/~duffield/pubs/DLT02-optimal.pdf
>>
>>and I wondered whether this IMRG is the right place to discuss
>>about it.
>>    
>>
>
>Indeed this is the right place to discuss such things.
>
>allman
>
>
>--
>Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/
>  
>
Actually, what I would try to discuss is if there's the need, in the 
standards, to agree on common procedures for coupling packet sampling 
and flow selection.
To better clarify, I copy hereafter a section that has been introduced 
in the last revision of the PSAMP draft
http://www.ietf.org/internet-drafts/draft-ietf-psamp-sample-tech-02.txt
that I'm co-authoring.
I'm trying to get some reaction about this in the IETF but also some 
discussion in this IMRG would help.
P.S.: is there any planned meeting in Vienna?
Regards,
Maurizio Molina

****************
3.1.2.2.3    Non-Uniform flow State dependent sampling

Another type of sampling that can be classified as Non-Uniform (and, 
possibly, probabilistic) is closely related to the flow concept as 
defined in [QuZC02], and it is only used jointly with a flow monitoring 
function (IPFIX monitoring function). Packets are selected, 
probabilistically or deterministically, dependent on a selection state. 
The point, here, is that the selection state is determined also by the 
state of the flow the packet belongs to and/or by the state of the other 
flows currently being monitored by the associated flow monitoring 
function. This type of sampling is also content dependent because the 
identification of the flow the packet belongs to requires analyzing part 
of the packet content. If the packet is selected, then it is passed as 
an input to the IPFIX monitoring function (this is called "Local Export" 
in [DuGG03].
Selecting the packet depending on the state of a flow cache is useful 
when memory resources of the flow monitoring function are scarce (i.e. 
there's no room to keep all the flows that have been scheduled for 
monitoring). The algorithms leading to the selection decision are not 
subject to standardization, but they may take into account factors like 
flow volume, flow grow rate, flow monitoring priority. An example of 
such an algorithm is described in [EsVa01].



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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body>
<br>
<br>
Mark Allman wrote:<br>
<blockquote type="cite"
 cite="mid20030530132952.C71D66B17A@lawyers.ir.bbn.com">
  <blockquote type="cite">
    <pre wrap="">As far as I know IPFIX deals with reporting per flow information,
PSAMP with sampling and reporting per packet information, selected
with some criteria.  Has there in any of these groups (or
elsewhere) been any discussion about FLOW sampling? I've seen
papers about it, e.g.

<a class="moz-txt-link-freetext" href="http://www.research.att.com/~duffield/pubs/DLT02-optimal.pdf">http://www.research.att.com/~duffield/pubs/DLT02-optimal.pdf</a>

and I wondered whether this IMRG is the right place to discuss
about it.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Indeed this is the right place to discuss such things.

allman


--
Mark Allman -- BBN/NASA GRC -- <a class="moz-txt-link-freetext" href="http://roland.grc.nasa.gov/~mallman/">http://roland.grc.nasa.gov/~mallman/</a>
  </pre>
</blockquote>
Actually, what I would try to discuss is if there's the need, in the standards, 
to agree on common procedures for coupling packet sampling and flow selection.<br>
 To better clarify, I copy hereafter a section that has been introduced in
the last revision of the PSAMP draft <br>
 <a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-ietf-psamp-sample-tech-02.txt">http://www.ietf.org/internet-drafts/draft-ietf-psamp-sample-tech-02.txt</a><br>
 that I'm co-authoring.<br>
I'm trying to get some reaction about this in the IETF but also some discussion
in this IMRG would help.<br>
P.S.: is there any planned meeting in Vienna?<br>
Regards,<br>
Maurizio Molina<br>
<br>
****************<br>
3.1.2.2.3&nbsp;&nbsp;&nbsp; Non-Uniform flow State dependent sampling <br>
 <br>
 Another type of sampling that can be classified as Non-Uniform (and, possibly, 
probabilistic) is closely related to the flow concept as defined in [QuZC02], 
and it is only used jointly with a flow monitoring function (IPFIX monitoring 
function). Packets are selected, probabilistically or deterministically, dependent
on a selection state. The point, here, is that the selection state is determined
also by the state of the flow the packet belongs to and/or by the state of
the other flows currently being monitored by the associated flow monitoring
function. This type of sampling is also content dependent because the identification
of the flow the packet belongs to requires analyzing part of the packet content.
If the packet is selected, then it is passed as an input to the IPFIX monitoring
function (this is called &#8220;Local Export&#8221; in [DuGG03].<br>
 Selecting the packet depending on the state of a flow cache is useful when 
memory resources of the flow monitoring function are scarce (i.e. there&#8217;s 
no room to keep all the flows that have been scheduled for monitoring). The 
algorithms leading to the selection decision are not subject to standardization, 
but they may take into account factors like flow volume, flow grow rate, flow
monitoring priority. An example of such an algorithm is described in [EsVa01].
<br>
 <br>
<pre class="moz-signature" cols="$mailwrapcol">
</pre>
<br>
</body>
</html>

--------------050805060509070506030408--


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



From exim@www1.ietf.org  Wed Jul  2 12:31:36 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 MAA00182
	for <imrg-archive@odin.ietf.org>; Wed, 2 Jul 2003 12:31:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XkVh-0004lB-EP
	for imrg-archive@odin.ietf.org; Wed, 02 Jul 2003 12:31:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h62GV96N018291
	for imrg-archive@odin.ietf.org; Wed, 2 Jul 2003 12:31:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XkVh-0004kw-9z
	for imrg-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 12:31:09 -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 MAA00166
	for <imrg-web-archive@ietf.org>; Wed, 2 Jul 2003 12:31:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XkVf-0003d9-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 12:31:08 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XkVf-0003d6-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 12:31:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XkVZ-0004ic-Gi; Wed, 02 Jul 2003 12:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XkVS-0004he-NP
	for imrg@optimus.ietf.org; Wed, 02 Jul 2003 12:30:54 -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 MAA00146
	for <imrg@ietf.org>; Wed, 2 Jul 2003 12:30:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XkVR-0003cr-00
	for imrg@ietf.org; Wed, 02 Jul 2003 12:30:53 -0400
Received: from seraph2.grc.nasa.gov ([128.156.10.11])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XkVL-0003cJ-00
	for imrg@ietf.org; Wed, 02 Jul 2003 12:30:47 -0400
Received: from lombok-fi.lerc.nasa.gov (lombok-fi.grc.nasa.gov [139.88.112.33])
	by seraph2.grc.nasa.gov (Postfix) with ESMTP id 782F0689DD
	for <imrg@ietf.org>; Wed,  2 Jul 2003 12:29:53 -0400 (EDT)
Received: from guns.grc.nasa.gov (guns.grc.nasa.gov [139.88.122.88])
	by lombok-fi.lerc.nasa.gov (NASA GRC 8.12.9/8.12.3) with ESMTP id h62GTruW018467
	for <imrg@ietf.org>; Wed, 2 Jul 2003 12:29:53 -0400 (EDT)
Received: from guns.lerc.nasa.gov (localhost.lerc.nasa.gov [127.0.0.1])
	by guns.grc.nasa.gov (Postfix) with ESMTP id EB4FA3BB3CD
	for <imrg@ietf.org>; Wed,  2 Jul 2003 12:29:52 -0400 (EDT)
To: imrg@ietf.org
From: Mark Allman <mallman@grc.nasa.gov>
Reply-To: mallman@grc.nasa.gov
Organization: BBN Technologies/NASA GRC
Song-of-the-Day: Lucky Ones
Date: Wed, 02 Jul 2003 12:29:52 -0400
Message-Id: <20030702162952.EB4FA3BB3CD@guns.grc.nasa.gov>
Subject: [IMRG] rg kick
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>

 
Folks-

In the spirit of getting the RG a bit more active I am going to kick
off a bit of a thought exercise in the next email about what sorts
of things the Internet community needs from the measurement
community (more info forthcoming).

In addition, I'd like to (re-)invite folks to think about their
measurement activites in the context of the IMRG and figure out if
the RG can make a meaningful contribution to those projects.  I'd
like to see the RG add some value to various pieces of measurement
work and believe that it can do so.  I'd be happy to chat with
anyone who is interested on working on projects with the RG.

Finally, as always, feel free to dump preliminary work or ideas or
pointers to draft papers or whatever on the mailing list.  I bet the
list can be useful for vetting preliminary work/ideas.

Thanks in advance!

allman
(imrg chair)


--
Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/

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



From exim@www1.ietf.org  Wed Jul  2 12:32:29 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 MAA00244
	for <imrg-archive@odin.ietf.org>; Wed, 2 Jul 2003 12:32:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XkWY-0004yG-JZ
	for imrg-archive@odin.ietf.org; Wed, 02 Jul 2003 12:32:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h62GW28G019102
	for imrg-archive@odin.ietf.org; Wed, 2 Jul 2003 12:32:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XkWY-0004y1-FH
	for imrg-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 12:32: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 MAA00229
	for <imrg-web-archive@ietf.org>; Wed, 2 Jul 2003 12:31:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XkWX-0003eG-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 12:32:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XkWW-0003eD-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 12:32:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XkWW-0004to-Sd; Wed, 02 Jul 2003 12:32:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XkVc-0004kI-Po
	for imrg@optimus.ietf.org; Wed, 02 Jul 2003 12:31: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 MAA00152
	for <imrg@ietf.org>; Wed, 2 Jul 2003 12:31:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XkVb-0003cx-00
	for imrg@ietf.org; Wed, 02 Jul 2003 12:31:03 -0400
Received: from seraph3.grc.nasa.gov ([128.156.10.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XkVV-0003cQ-00
	for imrg@ietf.org; Wed, 02 Jul 2003 12:30:57 -0400
Received: from lombok-fi.lerc.nasa.gov (lombok-fi.grc.nasa.gov [139.88.112.33])
	by seraph3.grc.nasa.gov (Postfix) with ESMTP id 75E7E6BA29
	for <imrg@ietf.org>; Wed,  2 Jul 2003 12:30:01 -0400 (EDT)
Received: from guns.grc.nasa.gov (guns.grc.nasa.gov [139.88.122.88])
	by lombok-fi.lerc.nasa.gov (NASA GRC 8.12.9/8.12.3) with ESMTP id h62GU1uW018508
	for <imrg@ietf.org>; Wed, 2 Jul 2003 12:30:01 -0400 (EDT)
Received: from guns.lerc.nasa.gov (localhost.lerc.nasa.gov [127.0.0.1])
	by guns.grc.nasa.gov (Postfix) with ESMTP id DD37C3BB3CD
	for <imrg@ietf.org>; Wed,  2 Jul 2003 12:30:00 -0400 (EDT)
To: imrg@ietf.org
From: Mark Allman <mallman@grc.nasa.gov>
Reply-To: mallman@grc.nasa.gov
Organization: BBN Technologies/NASA GRC
Song-of-the-Day: Lucky Ones
Date: Wed, 02 Jul 2003 12:30:00 -0400
Message-Id: <20030702163000.DD37C3BB3CD@guns.grc.nasa.gov>
Subject: [IMRG] Internet measurement: what next?
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>

 
I am interested in seeing some discussion about the fairly generic
topic of what sorts of outstanding problems exist in Internet
measurement:

    What are the core problems we need to solve?  
    What do we need to be able to measure that we cannot measure
      very well today?  
    Why?  
    What are the problems in taking measurements?  
    What can be done about those problems?
    What are practical problems that prevent wide-scale network
      measurement?
    What new tools does the community need to take, use, share and
      store measurements?

Please jump in with answers o any or all of the above.  Or, even
with additional big-picture sorts of questions of your own.

Thanks!

allman
(imrg chair)


--
Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/

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



From exim@www1.ietf.org  Wed Jul  2 14:15:33 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 OAA05048
	for <imrg-archive@odin.ietf.org>; Wed, 2 Jul 2003 14:15:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Xm8H-0003Yd-NA
	for imrg-archive@odin.ietf.org; Wed, 02 Jul 2003 14:15:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h62IF52O013669
	for imrg-archive@odin.ietf.org; Wed, 2 Jul 2003 14:15:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Xm8H-0003YO-J0
	for imrg-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 14:15:05 -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 OAA05016
	for <imrg-web-archive@ietf.org>; Wed, 2 Jul 2003 14:15:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xm8F-0005Ks-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 14:15:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xm8E-0005Kp-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 14:15:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Xm8D-0003Wz-0q; Wed, 02 Jul 2003 14:15:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Xm7g-0003WL-0p
	for imrg@optimus.ietf.org; Wed, 02 Jul 2003 14:14:28 -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 OAA04963
	for <imrg@ietf.org>; Wed, 2 Jul 2003 14:14:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xm7d-0005K0-00
	for imrg@ietf.org; Wed, 02 Jul 2003 14:14:25 -0400
Received: from telchemy.com ([66.155.69.251])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xm7c-0005J7-00
	for imrg@ietf.org; Wed, 02 Jul 2003 14:14:24 -0400
Received: from TELWS104 [64.238.103.215] by telchemy.com with ESMTP
  (SMTPD32-7.14) id A0B84B802A0; Wed, 02 Jul 2003 14:13:12 -0400
Reply-To: <alan@telchemy.com>
From: "Alan Clark" <alan@telchemy.com>
To: <mallman@grc.nasa.gov>, <imrg@ietf.org>
Subject: RE: [IMRG] Internet measurement: what next?
Date: Wed, 2 Jul 2003 14:04:47 -0400
Message-ID: <004901c340c4$6d22c9f0$6801a8c0@telchemy.com>
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.2800.1106
In-Reply-To: <20030702163000.DD37C3BB3CD@guns.grc.nasa.gov>
Content-Transfer-Encoding: 7bit
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Mark

In my opinion, current measures of PDV are not too useful when trying to
infer the effects of measured PDV on real time application performance.
This is partly due to the need to capture some aspects of the time varying
nature of PDV and it's impact on dynamic end systems such as de-jitter
buffers.  We've done some work in this space - notably developing an IP
network simulation model that can create delay traces that can closely
emulate captured traces, and using a "jitter envelope" to estimate jitter
(single point PDV measured with respect to a short term average delay) -
however we've only "scratched the surface" of the subject.
This is an important area to look at, given the emergence of a much wider
range of real time applications and the expected growth in voice, video,
netgames etc.

Alan Clark
Telchemy



-----Original Message-----
From: imrg-admin@ietf.org [mailto:imrg-admin@ietf.org]On Behalf Of Mark
Allman
Sent: Wednesday, July 02, 2003 12:30 PM
To: imrg@ietf.org
Subject: [IMRG] Internet measurement: what next?



I am interested in seeing some discussion about the fairly generic
topic of what sorts of outstanding problems exist in Internet
measurement:

    What are the core problems we need to solve?
    What do we need to be able to measure that we cannot measure
      very well today?
    Why?
    What are the problems in taking measurements?
    What can be done about those problems?
    What are practical problems that prevent wide-scale network
      measurement?
    What new tools does the community need to take, use, share and
      store measurements?

Please jump in with answers o any or all of the above.  Or, even
with additional big-picture sorts of questions of your own.

Thanks!

allman
(imrg chair)


--
Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/

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


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



From exim@www1.ietf.org  Wed Jul  2 14:37:31 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 OAA05700
	for <imrg-archive@odin.ietf.org>; Wed, 2 Jul 2003 14:37:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XmTY-00043m-31
	for imrg-archive@odin.ietf.org; Wed, 02 Jul 2003 14:37:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h62Ib4ms015600
	for imrg-archive@odin.ietf.org; Wed, 2 Jul 2003 14:37:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XmTX-00043X-Ta
	for imrg-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 14:37: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 OAA05683
	for <imrg-web-archive@ietf.org>; Wed, 2 Jul 2003 14:37:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XmTV-0005aR-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 14:37:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XmTU-0005aO-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 14:37:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XmTV-00041E-Ur; Wed, 02 Jul 2003 14:37:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XmSy-00040S-0s
	for imrg@optimus.ietf.org; Wed, 02 Jul 2003 14:36:28 -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 OAA05660
	for <imrg@ietf.org>; Wed, 2 Jul 2003 14:36:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XmSv-0005aC-00
	for imrg@ietf.org; Wed, 02 Jul 2003 14:36:25 -0400
Received: from smtp-out.sprintlabs.com ([208.30.172.76])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XmSu-0005Zs-00
	for imrg@ietf.org; Wed, 02 Jul 2003 14:36:24 -0400
Received: from mailman.sprintlabs.com (mx.sprintlabs.com [199.2.53.192])
	by smtp-out.sprintlabs.com (Postfix) with ESMTP
	id 7BB96B80A4; Wed,  2 Jul 2003 11:36:35 -0700 (PDT)
Received: by mailman.sprintlabs.com with Internet Mail Service (5.5.2656.59)
	id <MY197BGA>; Wed, 2 Jul 2003 11:35:52 -0700
Received: from IPTOSH1 (ip-tosh-1.sprintlabs.com [199.2.53.185]) by mailman.sprintlabs.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59)
	id MY197BF9; Wed, 2 Jul 2003 11:35:49 -0700
From: Supratik Bhattacharyya <Supratik@sprintlabs.com>
To: mallman@grc.nasa.gov, imrg@ietf.org
Cc: Christophe Diot <christophe.diot@intel.com>,
        Supratik Bhattacharyya <Supratik@sprintlabs.com>,
        Gianluca Iannaccone <gianluca@sprintlabs.com>
Subject: RE: [IMRG] Internet measurement: what next?
Date: Wed, 2 Jul 2003 11:35:48 -0700
Message-ID: <7F2A07FEA8F5624E887FE460E6E0527DCDF53E@PDAWB06C.ad.sprint.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030702163000.DD37C3BB3CD@guns.grc.nasa.gov>
Content-Transfer-Encoding: 7bit
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

For a discussion on issues concerning the deployment of monitoring
infrastructure in large operational networks, please see:


1) "Network Measurement and Monitoring : A Sprint Perspective", S.
Bhattacharyya et al.
   Internet Draft draft-bhattacharyya-monitoring-sprint-01.  Available
at:
 
http://www.ietf.org/internet-drafts/draft-bhattacharyya-monitoring-sprin
t-01.txt
	
   ABSTRACT:

   This document provides an overview of network measurements and
   monitoring from the perspective of Sprint Advanced Technology Labs.
   It starts with a detailed discussion of the benefits of monitoring
   for an ISP's backbone and the type of measurements required for
   various tasks. It describes the tools and techniques currently in
   use, and then outlines what else is needed to meet the challenges of
   monitoring an operational network.

2) "Deployment of inter-operable and cost-effective monitoring
infrastructure in ISP networks". S. Bhattacharyya et al.  
   Internet Draft draft-bhattacharyya-monitoring-deployment-00.
Available at:
 
http://www.ietf.org/internet-drafts/draft-bhattacharyya-monitoring-deplo
yment-00.txt

   ABSTRACT:	
   This document identifies issues and concerns in monitoring ISP
   networks. It outlines the components of a monitoring infrastructure
   designed to support ISP requirements. It discusses deployment and
   inter-operability issues. Related IETF working groups are identified.
   The goal of this document is to open a discussion on whether there
   should be a BOF addressing this issue at the next IETF (Vienna, July
   2003).

A BOF named ISP Monitoring Infrastructure Deployment (ispmon) has been
scheduled at the upcoming IETF in Vienna (July 13-18, 2003) to discuss
issues concerning operational monitoring. For details, check
http://www.ietf.org

Regards,

Supratik



-----Original Message-----
From: imrg-admin@ietf.org [mailto:imrg-admin@ietf.org] On Behalf Of Mark
Allman
Sent: Wednesday, July 02, 2003 9:30 AM
To: imrg@ietf.org
Subject: [IMRG] Internet measurement: what next?


 
I am interested in seeing some discussion about the fairly generic topic
of what sorts of outstanding problems exist in Internet
measurement:

    What are the core problems we need to solve?  
    What do we need to be able to measure that we cannot measure
      very well today?  
    Why?  
    What are the problems in taking measurements?  
    What can be done about those problems?
    What are practical problems that prevent wide-scale network
      measurement?
    What new tools does the community need to take, use, share and
      store measurements?

Please jump in with answers o any or all of the above.  Or, even with
additional big-picture sorts of questions of your own.

Thanks!

allman
(imrg chair)


--
Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/

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

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



From exim@www1.ietf.org  Wed Jul  2 16:20: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 QAA11824
	for <imrg-archive@odin.ietf.org>; Wed, 2 Jul 2003 16:20: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 19Xo55-0001lH-FD
	for imrg-archive@odin.ietf.org; Wed, 02 Jul 2003 16:19:58 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h62KJtho006767
	for imrg-archive@odin.ietf.org; Wed, 2 Jul 2003 16:19:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Xo55-0001l4-As
	for imrg-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 16:19:55 -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 QAA11779
	for <imrg-web-archive@ietf.org>; Wed, 2 Jul 2003 16:19:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xo51-00071c-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 16:19:51 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xo51-00071Y-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 16:19:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Xo4D-0001eF-2m; Wed, 02 Jul 2003 16:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Xo3m-0001YV-Ba
	for imrg@optimus.ietf.org; Wed, 02 Jul 2003 16:18:34 -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 QAA11660
	for <imrg@ietf.org>; Wed, 2 Jul 2003 16:18:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xo3h-0006zx-00
	for imrg@ietf.org; Wed, 02 Jul 2003 16:18:29 -0400
Received: from smtp.slac.stanford.edu ([134.79.18.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xo3h-0006zt-00
	for imrg@ietf.org; Wed, 02 Jul 2003 16:18:29 -0400
Received: from CONVERSION-DAEMON.smtp.slac.stanford.edu by
 smtp.slac.stanford.edu (PMDF V6.1-1 #37665)
 id <0HHE00901Z2MXB@smtp.slac.stanford.edu> for imrg@ietf.org; Wed,
 02 Jul 2003 13:18:22 -0700 (PDT)
Received: from smtpserv1.slac.stanford.edu
 (smtpserv1.slac.stanford.edu [134.79.18.81]) by smtp.slac.stanford.edu
 (PMDF V6.1-1 #37665) with ESMTP id <0HHE0086UZ2MTY@smtp.slac.stanford.edu>;
 Wed, 02 Jul 2003 13:18:22 -0700 (PDT)
Received: from ATREUS.win.slac.stanford.edu ([134.79.16.83])
 by smtpserv1.slac.stanford.edu (PMDF V6.1-1 #37665)
 with ESMTP id <0HHE0007TZ2MEJ@smtpserv1.slac.stanford.edu>; Wed,
 02 Jul 2003 13:18:22 -0700 (PDT)
Received: by atreus.slac.stanford.edu with Internet Mail Service (5.5.2653.19)
	id <N1LMA395>; Wed, 02 Jul 2003 13:18:20 -0700
Content-return: allowed
Date: Wed, 02 Jul 2003 13:18:21 -0700
From: "Cottrell, Les" <cottrell@SLAC.Stanford.EDU>
Subject: RE: [IMRG] Internet measurement: what next?
To: "'mallman@grc.nasa.gov'" <mallman@grc.nasa.gov>, imrg@ietf.org
Message-id: 
 <2846497B437BF84BAD1A4CC407418D26028E4EAA@exchange1.slac.stanford.edu>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: text/plain
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

A few of us (k claffy, Hans Werner-Braun, Brian Tierney, Ronn Ritke and myself) recently made a presentation to the government Inter-agency Large Scale Networks (LSN) group on this topic. There were two presentations, one on the needs/challenges of End-to-end monitoring especially for high performance applilcations, the second on a more Network centric needs for consumer grade applications.  The former talk may be found at:
http://www.slac.stanford.edu/grp/scs/net/talk03/lsn-jun03.html or http://www.slac.stanford.edu/grp/scs/net/talk03/lsn-jun03.ppt
The latter may be found at:
http://www.caida.org/outreach/presentations/2003/lsn20030610/

-----Original Message-----
From: Mark Allman [mailto:mallman@grc.nasa.gov] 
Sent: Wednesday, July 02, 2003 9:30 AM
To: imrg@ietf.org
Subject: [IMRG] Internet measurement: what next?


 
I am interested in seeing some discussion about the fairly generic topic of what sorts of outstanding problems exist in Internet
measurement:

    What are the core problems we need to solve?  
    What do we need to be able to measure that we cannot measure
      very well today?  
    Why?  
    What are the problems in taking measurements?  
    What can be done about those problems?
    What are practical problems that prevent wide-scale network
      measurement?
    What new tools does the community need to take, use, share and
      store measurements?

Please jump in with answers o any or all of the above.  Or, even with additional big-picture sorts of questions of your own.

Thanks!

allman
(imrg chair)


--
Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/

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

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



From exim@www1.ietf.org  Wed Jul  2 21:41:33 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 VAA09870
	for <imrg-archive@odin.ietf.org>; Wed, 2 Jul 2003 21:41:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Xt5u-0000xT-A8
	for imrg-archive@odin.ietf.org; Wed, 02 Jul 2003 21:41:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h631f6Lb003679
	for imrg-archive@odin.ietf.org; Wed, 2 Jul 2003 21:41:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Xt5u-0000xG-6x
	for imrg-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 21:41:06 -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 VAA09848
	for <imrg-web-archive@ietf.org>; Wed, 2 Jul 2003 21:41:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xt5r-000106-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 21:41:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xt5q-000103-00
	for imrg-web-archive@ietf.org; Wed, 02 Jul 2003 21:41:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Xt5p-0000v6-PK; Wed, 02 Jul 2003 21:41:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Xpoc-0000tT-44
	for imrg@optimus.ietf.org; Wed, 02 Jul 2003 18:11: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 SAA23875
	for <imrg@ietf.org>; Wed, 2 Jul 2003 18:10:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XpoX-0002ji-00
	for imrg@ietf.org; Wed, 02 Jul 2003 18:10:57 -0400
Received: from login.caida.org ([192.172.226.78])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XpoW-0002jR-00
	for imrg@ietf.org; Wed, 02 Jul 2003 18:10:56 -0400
Received: from login.caida.org (localhost [127.0.0.1])
	by login.caida.org (8.12.9/8.12.9) with ESMTP id h62MAp2e027759
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 2 Jul 2003 15:10:51 -0700 (PDT)
Received: from localhost (nevil@localhost)
	by login.caida.org (8.12.9/8.12.9/Submit) with ESMTP id h62MAoC1027756;
	Wed, 2 Jul 2003 15:10:50 -0700 (PDT)
Date: Wed, 2 Jul 2003 15:10:50 -0700 (PDT)
From: Nevil Brownlee <nevil@caida.org>
To: Maurizio Molina <molina@ccrle.nec.de>
cc: mallman@grc.nasa.gov, <imrg@ietf.org>
Subject: Re: [IMRG] Flow sampling (or selection)
In-Reply-To: <3F01CF5B.8010104@ccrle.nec.de>
Message-ID: <Pine.BSF.4.44.0307021501580.26392-100000@login.caida.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>


Hi Maurizio et al:

I haven't seen much discussion of flow sampling, in the sense of
'deciding which flows should be exported' from a flow measuring
device.

There's been some recent work on determining which flows are
the most significant/interesting, e.g.
Cristian Estan's   www.icir.org/vern/imw2001-papers/71.pdf
and my "Dragonflies and Tortoises," IEEE Communications, October 2002

In my work with NeTraMet I've implemented a coarse filter for flows,
you can tell NeTraMet's meter reader to ignore flows which have seen
less than n packets, so you can ignore things like port scans and
concentrate of high-volume or long-running flows.

Mark's description of the IPFIX and PSAMP WGs (below) is about right;
IPFIX has recently published a set of four new drafts, you can find
them via the IETF WG pages.  But IPFIX hasn't considered the question
of flow sampling, and I guess it's out of scope for PSAMP (which looks
at packet sampling).

Cheers, Nevil

-------------------------------------------------------------
   Nevil Brownlee                     Internet Researcher
   Phone: (858) 534 8338                 CAIDA, San Diego


On Tue, 1 Jul 2003, Maurizio Molina wrote:

>
>
> Mark Allman wrote:
>
> >>As far as I know IPFIX deals with reporting per flow information,
> >>PSAMP with sampling and reporting per packet information, selected
> >>with some criteria.  Has there in any of these groups (or
> >>elsewhere) been any discussion about FLOW sampling? I've seen
> >>papers about it, e.g.
> >>
> >>http://www.research.att.com/~duffield/pubs/DLT02-optimal.pdf
> >>
> >>and I wondered whether this IMRG is the right place to discuss
> >>about it.
> >>
> >>
> >
> >Indeed this is the right place to discuss such things.
> >
> >allman
> >
> >
> >--
> >Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/
> >
> >
> Actually, what I would try to discuss is if there's the need, in the
> standards, to agree on common procedures for coupling packet sampling
> and flow selection.
> To better clarify, I copy hereafter a section that has been introduced
> in the last revision of the PSAMP draft
> http://www.ietf.org/internet-drafts/draft-ietf-psamp-sample-tech-02.txt
> that I'm co-authoring.
> I'm trying to get some reaction about this in the IETF but also some
> discussion in this IMRG would help.
> P.S.: is there any planned meeting in Vienna?
> Regards,
> Maurizio Molina
>
> ****************
> 3.1.2.2.3    Non-Uniform flow State dependent sampling
>
> Another type of sampling that can be classified as Non-Uniform (and,
> possibly, probabilistic) is closely related to the flow concept as
> defined in [QuZC02], and it is only used jointly with a flow monitoring
> function (IPFIX monitoring function). Packets are selected,
> probabilistically or deterministically, dependent on a selection state.
> The point, here, is that the selection state is determined also by the
> state of the flow the packet belongs to and/or by the state of the other
> flows currently being monitored by the associated flow monitoring
> function. This type of sampling is also content dependent because the
> identification of the flow the packet belongs to requires analyzing part
> of the packet content. If the packet is selected, then it is passed as
> an input to the IPFIX monitoring function (this is called "Local Export"
> in [DuGG03].
> Selecting the packet depending on the state of a flow cache is useful
> when memory resources of the flow monitoring function are scarce (i.e.
> there's no room to keep all the flows that have been scheduled for
> monitoring). The algorithms leading to the selection decision are not
> subject to standardization, but they may take into account factors like
> flow volume, flow grow rate, flow monitoring priority. An example of
> such an algorithm is described in [EsVa01].
>
>
>


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



From exim@www1.ietf.org  Thu Jul  3 11:38:12 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 LAA17758
	for <imrg-archive@odin.ietf.org>; Thu, 3 Jul 2003 11:38:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y69X-0003lV-Ry
	for imrg-archive@odin.ietf.org; Thu, 03 Jul 2003 11:37:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h63FbhUP014467
	for imrg-archive@odin.ietf.org; Thu, 3 Jul 2003 11:37:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y69X-0003lD-NI
	for imrg-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 11:37:43 -0400
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 LAA17723
	for <imrg-web-archive@ietf.org>; Thu, 3 Jul 2003 11:37:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y68s-0003aZ-EL; Thu, 03 Jul 2003 11:37:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y68m-0003Zf-0d
	for imrg@optimus.ietf.org; Thu, 03 Jul 2003 11:36:56 -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 LAA17623
	for <imrg@ietf.org>; Thu, 3 Jul 2003 11:36:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y68k-0000VZ-00
	for imrg@ietf.org; Thu, 03 Jul 2003 11:36:54 -0400
Received: from byron.heanet.ie ([193.1.219.90])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y68j-0000VA-00
	for imrg@ietf.org; Thu, 03 Jul 2003 11:36:53 -0400
Received: from dhcp181.heanet.ie ([193.1.219.181] helo=heanet.ie)
	by byron.heanet.ie with esmtp (Exim 4.05)
	id 19Y68c-0003zq-00; Thu, 03 Jul 2003 16:36:46 +0100
Message-ID: <3F044D75.90109@heanet.ie>
Date: Thu, 03 Jul 2003 16:36:21 +0100
From: Victor Reijs <victor.reijs@heanet.ie>
Organization: HEAnet Ltd
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mallman@grc.nasa.gov
CC: imrg@ietf.org
Subject: Re: [IMRG] Internet measurement: what next?
References: <20030702163000.DD37C3BB3CD@guns.grc.nasa.gov>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello Mark,

Here are activities started up within TF-NGN on measurement 
infrastructures and PERT (Performance Enhancement and response 
team). So these are the issues we find important to work on and 
which are not yet covered fully:
http://www.dante.net/tf-ngn/pert/
http://www.dante.net/tf-ngn/perfmonit/
and the below documend gives a general overview of our needs with 
regard to the above:
http://www.dante.net/tf-ngn/D9.7-test_traffic_measurement_tools.pdf

All the best,


Victor



Mark Allman wrote:
>  
> I am interested in seeing some discussion about the fairly generic
> topic of what sorts of outstanding problems exist in Internet
> measurement:
> 
>     What are the core problems we need to solve?  
>     What do we need to be able to measure that we cannot measure
>       very well today?  
>     Why?  
>     What are the problems in taking measurements?  
>     What can be done about those problems?
>     What are practical problems that prevent wide-scale network
>       measurement?
>     What new tools does the community need to take, use, share and
>       store measurements?
> 
> Please jump in with answers o any or all of the above.  Or, even
> with additional big-picture sorts of questions of your own.
> 
> Thanks!
> 
> allman
> (imrg chair)
> 
> 
> --
> Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/
> 
> _______________________________________________
> IMRG mailing list
> IMRG@ietf.org
> https://www1.ietf.org/mailman/listinfo/imrg
> 


-- 
PGP public key: 
http://www.heanet.ie/heanet/projects/nat_infrastruct/pubkey.html
H.323 GDS: <exit-zone> 00353 01101001


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



From exim@www1.ietf.org  Thu Jul  3 12:23:36 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 MAA21449
	for <imrg-archive@odin.ietf.org>; Thu, 3 Jul 2003 12:23:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y6rR-0006Fw-7L
	for imrg-archive@odin.ietf.org; Thu, 03 Jul 2003 12:23:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h63GN5wG024042
	for imrg-archive@odin.ietf.org; Thu, 3 Jul 2003 12:23:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y6rR-0006Fh-2j
	for imrg-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 12:23:05 -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 MAA21365
	for <imrg-web-archive@ietf.org>; Thu, 3 Jul 2003 12:23:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y6rP-0001sg-00
	for imrg-web-archive@ietf.org; Thu, 03 Jul 2003 12:23:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y6rP-0001sc-00
	for imrg-web-archive@ietf.org; Thu, 03 Jul 2003 12:23:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y6rM-0006EI-Lc; Thu, 03 Jul 2003 12:23:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y6qs-0006Dw-5u
	for imrg@optimus.ietf.org; Thu, 03 Jul 2003 12:22:30 -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 MAA21328
	for <imrg@ietf.org>; Thu, 3 Jul 2003 12:22:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y6qq-0001rN-00
	for imrg@ietf.org; Thu, 03 Jul 2003 12:22:28 -0400
Received: from tokyo.ccrle.nec.de ([195.37.70.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y6qp-0001pG-00
	for imrg@ietf.org; Thu, 03 Jul 2003 12:22:27 -0400
Received: from venus.office (venus.office [10.1.1.11])
	by tokyo.ccrle.nec.de (8.12.9/8.12.8) with ESMTP id h63GLcVI013010;
	Thu, 3 Jul 2003 18:21:39 +0200 (CEST)
Received: from ccrle.nec.de (molina.office [10.1.1.126])
	by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP
	id ABECE12C42; Thu,  3 Jul 2003 18:04:55 +0200 (CEST)
Message-ID: <3F04580E.8050701@ccrle.nec.de>
Date: Thu, 03 Jul 2003 18:21:34 +0200
From: Maurizio Molina <molina@ccrle.nec.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Nevil Brownlee <nevil@caida.org>
Cc: mallman@grc.nasa.gov, imrg@ietf.org
Subject: Re: [IMRG] Flow sampling (or selection)
References: <Pine.BSF.4.44.0307021501580.26392-100000@login.caida.org>
Content-Type: multipart/alternative;
 boundary="------------000608090303010809090506"
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>


--------------000608090303010809090506
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Nevil Brownlee wrote:

>Hi Maurizio et al:
>
>I haven't seen much discussion of flow sampling, in the sense of
>'deciding which flows should be exported' from a flow measuring
>device.
>
>There's been some recent work on determining which flows are
>the most significant/interesting, e.g.
>Cristian Estan's   www.icir.org/vern/imw2001-papers/71.pdf
>and my "Dragonflies and Tortoises," IEEE Communications, October 2002
>
>In my work with NeTraMet I've implemented a coarse filter for flows,
>you can tell NeTraMet's meter reader to ignore flows which have seen
>less than n packets, so you can ignore things like port scans and
>concentrate of high-volume or long-running flows.
>
>Mark's description of the IPFIX and PSAMP WGs (below) is about right;
>IPFIX has recently published a set of four new drafts, you can find
>them via the IETF WG pages.  But IPFIX hasn't considered the question
>of flow sampling, and I guess it's out of scope for PSAMP (which looks
>at packet sampling).
>
Nevil,
It's true that it's difficult to "position"  such a sampling 
methodology, that it's actually a sort of "packet sampling oriented to 
flow selection", but if  we believe it can play a role in future 
implementations we should try to do it. I think the best is to stimulate 
the discussion in both groups (PSAMP and IPFIX).
As regards PSAMP, it's true that the WG deals with packet sampling, but 
stateful sampling (e.g. sampling based on router state) has always been 
considered. Then, I tried to insert it in the draft this paragraph 
describing it as "flow state dependent sampling". Hope to get some 
reaction on this.
As regards IPFIX, it's true that IPFIX hasn't considered the question of 
flow sampling, but the requirement to do so is still there, also in the 
most recent version of the requirement draft, see 
draft-ietf-ipfix-reqs-10.txt, section 5.2 and 5.3.
On the 21.05.2003 I initiated a discussion on this on the IPFIX ML 
(inside a thread "changes to architecture doc.) getting some negative 
reactions (Ganesh Sadasivan, Carter Bullard) and a positive one (Alex 
Audu). Perhaps it'd be interesting to have your opinion as WG chair.
Regards,
Maurizio

>
>Cheers, Nevil
>
>-------------------------------------------------------------
>   Nevil Brownlee                     Internet Researcher
>   Phone: (858) 534 8338                 CAIDA, San Diego
>
>
>On Tue, 1 Jul 2003, Maurizio Molina wrote:
>
>  
>
>>Mark Allman wrote:
>>
>>    
>>
>>>>As far as I know IPFIX deals with reporting per flow information,
>>>>PSAMP with sampling and reporting per packet information, selected
>>>>with some criteria.  Has there in any of these groups (or
>>>>elsewhere) been any discussion about FLOW sampling? I've seen
>>>>papers about it, e.g.
>>>>
>>>>http://www.research.att.com/~duffield/pubs/DLT02-optimal.pdf
>>>>
>>>>and I wondered whether this IMRG is the right place to discuss
>>>>about it.
>>>>
>>>>
>>>>        
>>>>
>>>Indeed this is the right place to discuss such things.
>>>
>>>allman
>>>
>>>
>>>--
>>>Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/
>>>
>>>
>>>      
>>>
>>Actually, what I would try to discuss is if there's the need, in the
>>standards, to agree on common procedures for coupling packet sampling
>>and flow selection.
>>To better clarify, I copy hereafter a section that has been introduced
>>in the last revision of the PSAMP draft
>>http://www.ietf.org/internet-drafts/draft-ietf-psamp-sample-tech-02.txt
>>that I'm co-authoring.
>>I'm trying to get some reaction about this in the IETF but also some
>>discussion in this IMRG would help.
>>P.S.: is there any planned meeting in Vienna?
>>Regards,
>>Maurizio Molina
>>
>>****************
>>3.1.2.2.3    Non-Uniform flow State dependent sampling
>>
>>Another type of sampling that can be classified as Non-Uniform (and,
>>possibly, probabilistic) is closely related to the flow concept as
>>defined in [QuZC02], and it is only used jointly with a flow monitoring
>>function (IPFIX monitoring function). Packets are selected,
>>probabilistically or deterministically, dependent on a selection state.
>>The point, here, is that the selection state is determined also by the
>>state of the flow the packet belongs to and/or by the state of the other
>>flows currently being monitored by the associated flow monitoring
>>function. This type of sampling is also content dependent because the
>>identification of the flow the packet belongs to requires analyzing part
>>of the packet content. If the packet is selected, then it is passed as
>>an input to the IPFIX monitoring function (this is called "Local Export"
>>in [DuGG03].
>>Selecting the packet depending on the state of a flow cache is useful
>>when memory resources of the flow monitoring function are scarce (i.e.
>>there's no room to keep all the flows that have been scheduled for
>>monitoring). The algorithms leading to the selection decision are not
>>subject to standardization, but they may take into account factors like
>>flow volume, flow grow rate, flow monitoring priority. An example of
>>such an algorithm is described in [EsVa01].
>>
>>
>>
>>    
>>
>
>  
>




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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body>
<br>
<br>
Nevil Brownlee wrote:<br>
<blockquote type="cite"
 cite="midPine.BSF.4.44.0307021501580.26392-100000@login.caida.org">
  <pre wrap="">Hi Maurizio et al:

I haven't seen much discussion of flow sampling, in the sense of
'deciding which flows should be exported' from a flow measuring
device.

There's been some recent work on determining which flows are
the most significant/interesting, e.g.
Cristian Estan's   <a class="moz-txt-link-abbreviated" href="http://www.icir.org/vern/imw2001-papers/71.pdf">www.icir.org/vern/imw2001-papers/71.pdf</a>
and my "Dragonflies and Tortoises," IEEE Communications, October 2002

In my work with NeTraMet I've implemented a coarse filter for flows,
you can tell NeTraMet's meter reader to ignore flows which have seen
less than n packets, so you can ignore things like port scans and
concentrate of high-volume or long-running flows.

Mark's description of the IPFIX and PSAMP WGs (below) is about right;
IPFIX has recently published a set of four new drafts, you can find
them via the IETF WG pages.  But IPFIX hasn't considered the question
of flow sampling, and I guess it's out of scope for PSAMP (which looks
at packet sampling).</pre>
</blockquote>
Nevil,<br>
It's true that it's difficult to "position" &nbsp;such a sampling methodology,
that it's actually a sort of "packet sampling oriented to flow selection",
but if&nbsp;  we believe it can play a role in future implementations we should
try to do it. I think the best is to stimulate the discussion in both groups
(PSAMP and IPFIX).<br>
As regards PSAMP, it's true that the WG deals with packet sampling, but stateful
sampling (e.g. sampling based on router state) has always been considered.
 Then, I tried to insert it in the draft this paragraph describing it as
"flow state dependent sampling". Hope to get some reaction on this.<br>
As regards IPFIX, it's true that IPFIX hasn't considered the question of
flow sampling, but the requirement to do so is still there, also in the most
recent version of the requirement draft, see draft-ietf-ipfix-reqs-10.txt,
section 5.2 and 5.3. <br>
On the 21.05.2003 I initiated a discussion on this on the IPFIX ML (inside
a thread "changes to architecture doc.) getting some negative reactions (Ganesh
Sadasivan, Carter Bullard) and a positive one (Alex Audu). Perhaps it'd be
interesting to have your opinion as WG chair.<br>
Regards,<br>
Maurizio<br>
<blockquote type="cite"
 cite="midPine.BSF.4.44.0307021501580.26392-100000@login.caida.org">
  <pre wrap="">

Cheers, Nevil

-------------------------------------------------------------
   Nevil Brownlee                     Internet Researcher
   Phone: (858) 534 8338                 CAIDA, San Diego


On Tue, 1 Jul 2003, Maurizio Molina wrote:

  </pre>
  <blockquote type="cite">
    <pre wrap="">
Mark Allman wrote:

    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">As far as I know IPFIX deals with reporting per flow information,
PSAMP with sampling and reporting per packet information, selected
with some criteria.  Has there in any of these groups (or
elsewhere) been any discussion about FLOW sampling? I've seen
papers about it, e.g.

<a class="moz-txt-link-freetext" href="http://www.research.att.com/~duffield/pubs/DLT02-optimal.pdf">http://www.research.att.com/~duffield/pubs/DLT02-optimal.pdf</a>

and I wondered whether this IMRG is the right place to discuss
about it.


        </pre>
      </blockquote>
      <pre wrap="">Indeed this is the right place to discuss such things.

allman


--
Mark Allman -- BBN/NASA GRC -- <a class="moz-txt-link-freetext" href="http://roland.grc.nasa.gov/~mallman/">http://roland.grc.nasa.gov/~mallman/</a>


      </pre>
    </blockquote>
    <pre wrap="">Actually, what I would try to discuss is if there's the need, in the
standards, to agree on common procedures for coupling packet sampling
and flow selection.
To better clarify, I copy hereafter a section that has been introduced
in the last revision of the PSAMP draft
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-ietf-psamp-sample-tech-02.txt">http://www.ietf.org/internet-drafts/draft-ietf-psamp-sample-tech-02.txt</a>
that I'm co-authoring.
I'm trying to get some reaction about this in the IETF but also some
discussion in this IMRG would help.
P.S.: is there any planned meeting in Vienna?
Regards,
Maurizio Molina

****************
3.1.2.2.3    Non-Uniform flow State dependent sampling

Another type of sampling that can be classified as Non-Uniform (and,
possibly, probabilistic) is closely related to the flow concept as
defined in [QuZC02], and it is only used jointly with a flow monitoring
function (IPFIX monitoring function). Packets are selected,
probabilistically or deterministically, dependent on a selection state.
The point, here, is that the selection state is determined also by the
state of the flow the packet belongs to and/or by the state of the other
flows currently being monitored by the associated flow monitoring
function. This type of sampling is also content dependent because the
identification of the flow the packet belongs to requires analyzing part
of the packet content. If the packet is selected, then it is passed as
an input to the IPFIX monitoring function (this is called "Local Export"
in [DuGG03].
Selecting the packet depending on the state of a flow cache is useful
when memory resources of the flow monitoring function are scarce (i.e.
there's no room to keep all the flows that have been scheduled for
monitoring). The algorithms leading to the selection decision are not
subject to standardization, but they may take into account factors like
flow volume, flow grow rate, flow monitoring priority. An example of
such an algorithm is described in [EsVa01].



    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="$mailwrapcol">

</pre>
<br>
</body>
</html>

--------------000608090303010809090506--


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



From exim@www1.ietf.org  Thu Jul  3 13:21:41 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 NAA25963
	for <imrg-archive@odin.ietf.org>; Thu, 3 Jul 2003 13:21:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y7lg-0000RW-9T
	for imrg-archive@odin.ietf.org; Thu, 03 Jul 2003 13:21:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h63HLCxd001698
	for imrg-archive@odin.ietf.org; Thu, 3 Jul 2003 13:21:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y7lg-0000RJ-5u
	for imrg-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 13:21:12 -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 NAA25916
	for <imrg-web-archive@ietf.org>; Thu, 3 Jul 2003 13:21:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y7ld-0003o4-00
	for imrg-web-archive@ietf.org; Thu, 03 Jul 2003 13:21:09 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y7ld-0003ny-00
	for imrg-web-archive@ietf.org; Thu, 03 Jul 2003 13:21:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y7lV-0000Ps-HS; Thu, 03 Jul 2003 13:21:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y7lR-0000PL-WE
	for imrg@optimus.ietf.org; Thu, 03 Jul 2003 13:20:58 -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 NAA25863
	for <imrg@ietf.org>; Thu, 3 Jul 2003 13:20:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y7lP-0003nP-00
	for imrg@ietf.org; Thu, 03 Jul 2003 13:20:55 -0400
Received: from smtp-out.sprintlabs.com ([208.30.172.76])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y7lO-0003lv-00
	for imrg@ietf.org; Thu, 03 Jul 2003 13:20:54 -0400
Received: from mailman.sprintlabs.com (mx.sprintlabs.com [199.2.53.192])
	by smtp-out.sprintlabs.com (Postfix) with ESMTP id F10F0B810F
	for <imrg@ietf.org>; Thu,  3 Jul 2003 10:21:05 -0700 (PDT)
Received: by mailman.sprintlabs.com with Internet Mail Service (5.5.2656.59)
	id <MY1971QS>; Thu, 3 Jul 2003 10:20:22 -0700
Message-ID: <49D9473417F1234C9C86886EE8353FAAEFF69E@mailman.sprintlabs.com>
From: Gianluca Iannaccone <gianluca@sprintlabs.com>
To: "'imrg@ietf.org'" <imrg@ietf.org>
Date: Thu, 3 Jul 2003 10:20:21 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Subject: [IMRG] ispmon BOF
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>

[apologies if you receive multiple copies of this email]

please find attached the agenda and description of the 
new BOF on Monitoring Infrastructure Deployment. 

thanks,
gianluca



----------------------------------------------------------
Monitoring Infrastructure Deployment BOF (ispmon)

Thursday, July 17 at 1530-1730
===============================

CHAIR:	Gianluca Iannaccone <gianluca@sprintlabs.com>

AGENDA

  5 min - Agenda Bashing    
 15 min - Presentation: draft-bhattacharyya-monitoring-deployment-00
 10 min - Presentation: Sprint's Continuous Monitoring (CMON) project 
 15 min - Scope and candidate charter for Working group
 15 min - Next steps


MAILING LIST

 General Discussion: ispmon@ops.ietf.org
 To Subscribe: ispmon-request@ops.ietf.org, "subscribe" in body
 Archive: http://opt.ietf.org/lists/ispmon


DESCRIPTION 

Various types of measurement data need to be collected to support 
monitoring applications.  We classified them in two broad categories: 
(i) aggregate information that need to be collected at coarse time-scales 
and reported on a regular basis (e.g. SNMP, flows, routing tables) ; 
(ii) packet-level traces to analyze and understand a specific phenomenon.

There are a number of implementation challenges in order to capture,
process, summarize and export data at the required level of granularity
at the time that it is needed. Some of these problems are being
addressed in different IETF working groups whereas some others have 
not been.

The goal of this BOF is to discuss whether a new working group is needed 
to undertake the following activities: (i) define a framework for
monitoring needed to support day-to-day operations in IP networks, (ii)
identify existing and on-going efforts in the IETF on various aspects of
the framework and ensure that this work guarantees inter-operability
among ISPs, and (iii) provide clear guidelines to equipment vendors on
what infrastructure is needed to support monitoring in ISP networks.

A charter for the new working group could address (but not be limited to)
the following aspects: 

 .  provide BCP documents on how to instrument monitoring systems in 
    large-scale provider networks. 

 .  describe known-to-work implementations and identify open issues. 

 .  specify components of an operational monitoring infrastructure
    in particular regarding aspects not addressed in other IETF WGs 
    (e.g., storage, aging and analysis of collected data, control 
    plane functionality).

 .  specify ways for ISPs to share monitoring data. 

 .  make recommendations to other working groups standardizing different
    elements of monitoring, e.g., IPPM, IPFIX and PSAMP, INCH, IDWG, etc.,


READING LIST

 . draft-bhattacharyya-monitoring-deployment-00.txt
 . draft-bhattacharyya-monitoring-sprint-01.txt
 . draft-ietf-ipfix-reqs-10.txt
 . draft-ietf-psamp-framework-03.txt
 . draft-ietf-idwg-requirements-10.txt
 . draft-ietf-inch-iodef-01.txt 
 . RFC2330: Framework for IP Performance Metrics 
 
RELATED WGs

 IP Flow Information Export (ipfix)
 http://www.ietf.org/html.charters/ipfix-charter.html

 Packet Sampling (psamp)
 http://www.ietf.org/html.charters/psamp-charter.html
 
 IP Performance Metrics (ippm)
 http://www.ietf.org/html.charters/ippm-charter.html

 Intrusion Detection Exchange Format (idwg)
 http://www.ietf.org/html.charters/idwg-charter.html

 Extended Incident Handling (inch)
 http://www.ietf.org/html.charters/inch-charter.html





----------------------------------------------------------
Gianluca Iannaccone      '         gianluca@sprintlabs.com
Sprint ATL               '           tel +1 (650) 375-4198
1 Adrian Court           '           fax +1 (650) 375-4079
Burlingame, CA 94010     '    www.sprintlabs.com/~gianluca

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



From exim@www1.ietf.org  Thu Jul  3 15:30:38 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 PAA03227
	for <imrg-archive@odin.ietf.org>; Thu, 3 Jul 2003 15:30:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y9mS-0005my-Mr
	for imrg-archive@odin.ietf.org; Thu, 03 Jul 2003 15:30:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h63JU8S4022248
	for imrg-archive@odin.ietf.org; Thu, 3 Jul 2003 15:30:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y9mS-0005ml-HE
	for imrg-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 15:30:08 -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 PAA03207
	for <imrg-web-archive@ietf.org>; Thu, 3 Jul 2003 15:30:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y9mR-000050-00
	for imrg-web-archive@ietf.org; Thu, 03 Jul 2003 15:30:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y9mQ-00004x-00
	for imrg-web-archive@ietf.org; Thu, 03 Jul 2003 15:30:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y9mL-0005lF-Pv; Thu, 03 Jul 2003 15:30:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y9lq-0005kk-U5
	for imrg@optimus.ietf.org; Thu, 03 Jul 2003 15:29:31 -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 PAA03181
	for <imrg@ietf.org>; Thu, 3 Jul 2003 15:29:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y9lp-00004Z-00
	for imrg@ietf.org; Thu, 03 Jul 2003 15:29:29 -0400
Received: from seraph3.grc.nasa.gov ([128.156.10.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y9lo-00004H-00
	for imrg@ietf.org; Thu, 03 Jul 2003 15:29:28 -0400
Received: from lombok-fi.lerc.nasa.gov (lombok-fi.grc.nasa.gov [139.88.112.33])
	by seraph3.grc.nasa.gov (Postfix) with ESMTP id 0BE8D6BA9E
	for <imrg@ietf.org>; Thu,  3 Jul 2003 15:28:55 -0400 (EDT)
Received: from guns.grc.nasa.gov (guns.grc.nasa.gov [139.88.122.88])
	by lombok-fi.lerc.nasa.gov (NASA GRC 8.12.9/8.12.9) with ESMTP id h63JSsWD028913
	for <imrg@ietf.org>; Thu, 3 Jul 2003 15:28:54 -0400 (EDT)
Received: from guns.lerc.nasa.gov (localhost.lerc.nasa.gov [127.0.0.1])
	by guns.grc.nasa.gov (Postfix) with ESMTP id 5519E3BB3CD
	for <imrg@ietf.org>; Thu,  3 Jul 2003 15:28:54 -0400 (EDT)
To: imrg@ietf.org
From: Mark Allman <mallman@grc.nasa.gov>
Reply-To: mallman@grc.nasa.gov
Subject: Nevil Brownlee: Re: [IMRG] Flow sampling (or selection)
Organization: BBN Technologies/NASA GRC
Song-of-the-Day: Smoke
Date: Thu, 03 Jul 2003 15:28:54 -0400
Message-Id: <20030703192854.5519E3BB3CD@guns.grc.nasa.gov>
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>

 
[This got caught in the filters.  I approved it last night, but
 don't see it in the IMRG mail archive and so fear that it did not
 make it to the list.  I'm off to look into it... if this is, in
 fact, a repeat, I appologize.]


------- Forwarded Message

Date: Wed, 2 Jul 2003 15:10:50 -0700 (PDT)
From: Nevil Brownlee <nevil@caida.org>
To: Maurizio Molina <molina@ccrle.nec.de>
Cc: mallman@grc.nasa.gov, <imrg@ietf.org>
Subject: Re: [IMRG] Flow sampling (or selection)


Hi Maurizio et al:

I haven't seen much discussion of flow sampling, in the sense of
'deciding which flows should be exported' from a flow measuring
device.

There's been some recent work on determining which flows are
the most significant/interesting, e.g.
Cristian Estan's   www.icir.org/vern/imw2001-papers/71.pdf
and my "Dragonflies and Tortoises," IEEE Communications, October 2002

In my work with NeTraMet I've implemented a coarse filter for flows,
you can tell NeTraMet's meter reader to ignore flows which have seen
less than n packets, so you can ignore things like port scans and
concentrate of high-volume or long-running flows.

Mark's description of the IPFIX and PSAMP WGs (below) is about right;
IPFIX has recently published a set of four new drafts, you can find
them via the IETF WG pages.  But IPFIX hasn't considered the question
of flow sampling, and I guess it's out of scope for PSAMP (which looks
at packet sampling).

Cheers, Nevil

- -------------------------------------------------------------
   Nevil Brownlee                     Internet Researcher
   Phone: (858) 534 8338                 CAIDA, San Diego


On Tue, 1 Jul 2003, Maurizio Molina wrote:

>
>
> Mark Allman wrote:
>
> >>As far as I know IPFIX deals with reporting per flow information,
> >>PSAMP with sampling and reporting per packet information, selected
> >>with some criteria.  Has there in any of these groups (or
> >>elsewhere) been any discussion about FLOW sampling? I've seen
> >>papers about it, e.g.
> >>
> >>http://www.research.att.com/~duffield/pubs/DLT02-optimal.pdf
> >>
> >>and I wondered whether this IMRG is the right place to discuss
> >>about it.
> >>
> >>
> >
> >Indeed this is the right place to discuss such things.
> >
> >allman
> >
> >
> >--
> >Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/
> >
> >
> Actually, what I would try to discuss is if there's the need, in the
> standards, to agree on common procedures for coupling packet sampling
> and flow selection.
> To better clarify, I copy hereafter a section that has been introduced
> in the last revision of the PSAMP draft
> http://www.ietf.org/internet-drafts/draft-ietf-psamp-sample-tech-02.txt
> that I'm co-authoring.
> I'm trying to get some reaction about this in the IETF but also some
> discussion in this IMRG would help.
> P.S.: is there any planned meeting in Vienna?
> Regards,
> Maurizio Molina
>
> ****************
> 3.1.2.2.3    Non-Uniform flow State dependent sampling
>
> Another type of sampling that can be classified as Non-Uniform (and,
> possibly, probabilistic) is closely related to the flow concept as
> defined in [QuZC02], and it is only used jointly with a flow monitoring
> function (IPFIX monitoring function). Packets are selected,
> probabilistically or deterministically, dependent on a selection state.
> The point, here, is that the selection state is determined also by the
> state of the flow the packet belongs to and/or by the state of the other
> flows currently being monitored by the associated flow monitoring
> function. This type of sampling is also content dependent because the
> identification of the flow the packet belongs to requires analyzing part
> of the packet content. If the packet is selected, then it is passed as
> an input to the IPFIX monitoring function (this is called "Local Export"
> in [DuGG03].
> Selecting the packet depending on the state of a flow cache is useful
> when memory resources of the flow monitoring function are scarce (i.e.
> there's no room to keep all the flows that have been scheduled for
> monitoring). The algorithms leading to the selection decision are not
> subject to standardization, but they may take into account factors like
> flow volume, flow grow rate, flow monitoring priority. An example of
> such an algorithm is described in [EsVa01].
>
>
>

------- End of Forwarded Message


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



From exim@www1.ietf.org  Thu Jul  3 15:39:35 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 PAA03541
	for <imrg-archive@odin.ietf.org>; Thu, 3 Jul 2003 15:39:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y9v5-0006ty-My
	for imrg-archive@odin.ietf.org; Thu, 03 Jul 2003 15:39:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h63Jd3VC026524
	for imrg-archive@odin.ietf.org; Thu, 3 Jul 2003 15:39:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y9v5-0006tj-Jm
	for imrg-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 15:39: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 PAA03525
	for <imrg-web-archive@ietf.org>; Thu, 3 Jul 2003 15:39:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y9v4-0000Lo-00
	for imrg-web-archive@ietf.org; Thu, 03 Jul 2003 15:39:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y9v3-0000Ll-00
	for imrg-web-archive@ietf.org; Thu, 03 Jul 2003 15:39:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y9v2-0006q0-SG; Thu, 03 Jul 2003 15:39:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Y9v2-0006pp-8c
	for imrg@optimus.ietf.org; Thu, 03 Jul 2003 15:39:00 -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 PAA03515
	for <imrg@ietf.org>; Thu, 3 Jul 2003 15:38:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y9v0-0000Lh-00
	for imrg@ietf.org; Thu, 03 Jul 2003 15:38:58 -0400
Received: from relay.jaalam.net ([209.139.228.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y9v0-0000La-00
	for imrg@ietf.org; Thu, 03 Jul 2003 15:38:58 -0400
Received: from jsrvr8.jaalam.net ([172.16.128.105]) by relay.jaalam.net with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 3 Jul 2003 12:38:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 3 Jul 2003 12:38:27 -0700
Message-ID: <F09324DCDD2F5D488EAC603D6B299DC71AF69A@jsrvr8.jaalam.net>
Thread-Topic: Internet measurement: what next? - Designing for Visibility
Thread-Index: AcNBfN2Hped7fnraS+ufB4TTCsDpugADt8uQ
From: "Loki Jorgenson" <ljorgenson@jaalam.com>
To: <imrg@ietf.org>
X-OriginalArrivalTime: 03 Jul 2003 19:38:52.0781 (UTC) FILETIME=[BBC959D0:01C3419A]
Content-Transfer-Encoding: quoted-printable
Subject: [IMRG] RE: Internet measurement: what next? - Designing for Visibility
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Mark - a theme worth considering IHMO is designing networks for
visibilty.

Many of the best and most basic sources of network intelligence are
being impacted by changes in network design.  Take ICMP for example - it
is effectively the nervous system of the networks.  It does the job of
feedback for network components.  In some ways, it is like tactile
sensation in the human body that allows us to interact effectively (and
safely) with our environment.

However, even the simplest means, such as ping and traceroute, are being
affected by the use of VPNs and VLANs, traffic shaping and filtering,
aggregate routing with multiple peering points, ICMP blocking, parallel
channels on routers, lightpaths, etc.  Obviously there are reasons and
benefits for these technologies to be introduced.  Security is one of
the driving forces.  At one extreme, ICMP may be blocked completely -
this is a bit like numbing all the nerves in the body in order to avoid
pain.  There is a balance to be struck.

Currently the means to effective monitoring, measurement,
troubleshooting and tuning are actively being developed.  Most rely on
the essential (and changing) nature of networks at various layers.  Some
require access to networks that aren't always feasible or have limiting
constraints (e.g. you must own the hardware).  Networks can support
these capabilities better or worse in the future.

And then there are all kinds of proposals/drafts that would affect
stacks, hardware, and application design and might provide new forms of
feedback.  These typically require widespread adoption and even then the
overall macroscopic consequences are not well understood (e.g. what does
a world of coexisting legacy and Fast TCP stacks look like?).  What do
they offer?

So, going forward, one of the chief questions then becomes "How can
(typical/IP) networks be optimized for various benefits including
effective feedback mechanisms that support monitoring, measurement,
diagnosis and tuning?"   In a future with self-healing or self-tuning
networks, this seems tremendously important.

I would be interested to hear if any comments....

Loki Jorgenson
Director, Research
jaalaM Technologies
t   604 433 2333 ext 105
m   604 340-2480


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



From exim@www1.ietf.org  Sun Jul  6 23:51:14 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 XAA29162
	for <imrg-archive@odin.ietf.org>; Sun, 6 Jul 2003 23:51:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZN1b-0003aF-Os
	for imrg-archive@odin.ietf.org; Sun, 06 Jul 2003 23:50:47 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h673ol6B013776
	for imrg-archive@odin.ietf.org; Sun, 6 Jul 2003 23:50:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZN1b-0003a7-Ki
	for imrg-web-archive@optimus.ietf.org; Sun, 06 Jul 2003 23:50:47 -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 XAA29145
	for <imrg-web-archive@ietf.org>; Sun, 6 Jul 2003 23:50:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZN1Z-00076c-00
	for imrg-web-archive@ietf.org; Sun, 06 Jul 2003 23:50:45 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZN1Y-00076Z-00
	for imrg-web-archive@ietf.org; Sun, 06 Jul 2003 23:50:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZN0r-0003W7-LJ; Sun, 06 Jul 2003 23:50:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZN09-0003Vg-CY
	for imrg@optimus.ietf.org; Sun, 06 Jul 2003 23:49:18 -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 XAA29131
	for <imrg@ietf.org>; Sun, 6 Jul 2003 23:49:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZN07-00076E-00
	for imrg@ietf.org; Sun, 06 Jul 2003 23:49:15 -0400
Received: from h-135-207-24-16.research.att.com ([135.207.24.16] helo=linux.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZN06-000760-00
	for imrg@ietf.org; Sun, 06 Jul 2003 23:49:14 -0400
Received: from unixmail.research.att.com (unixmail.research.att.com [135.207.26.71])
	by linux.research.att.com (8.12.8/8.12.8) with ESMTP id h6741KJh023774;
	Mon, 7 Jul 2003 00:01:20 -0400
Received: from chips.research.att.com (chips.research.att.com [135.207.27.139])
	by unixmail.research.att.com (8.12.8+Sun/8.8.7) with ESMTP id h673mdXs029564;
	Sun, 6 Jul 2003 23:48:39 -0400 (EDT)
Received: (from jrex@localhost)
	by chips.research.att.com (SGI-8.9.3/8.8.5) id XAA03941;
	Sun, 6 Jul 2003 23:48:44 -0400 (EDT)
Date: Sun, 6 Jul 2003 23:48:44 -0400 (EDT)
Message-Id: <200307070348.XAA03941@chips.research.att.com>
From: Jennifer Rexford <jrex@research.att.com>
To: ljorgenson@jaalam.com
CC: imrg@ietf.org
Subject: Re: [IMRG] RE: Internet measurement: what next? - Designing for Visibility
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>

> a theme worth considering IHMO is designing networks for visibilty.

I think that's a great point.  Measurement has been largely an
afterthought (and an "add on") in designing IP networks and, as such,
our visibility is pretty limited and imperfect.  In some cases, we can
"add" measurement by tapping the network or monitoring the protocols.
But, troubleshooting problems in the network is much harder and it
would be interesting to think of how to extend the equipment and the
protocols to report more information (e.g., error messages, protocol
annotations, etc.) that would help in diagnosing problems -- or to
better enable active tools like traceroute to work.

> However, even the simplest means, such as ping and traceroute, are being
> affected by the use of VPNs and VLANs, traffic shaping and filtering,
> aggregate routing with multiple peering points, ICMP blocking, parallel
> channels on routers, lightpaths, etc.

Good point.  Along these lines, a group of us have been working on 
a tool that reports the sequence of Autonomous Systems (ASes) on a
forwarding path, to help in determining which AS (or ASes) or
involved.  See

  Z. M. Mao, J. Rexford, J. Wang, and R. H. Katz, "Towards an
  Accurate AS-Level Traceroute Tool," to appear in Proc. ACM
  SIGCOMM, August 2003.
    http://www.research.att.com/~jrex/papers/sigcomm03.ps
    http://www.research.att.com/~jrex/papers/sigcomm03.pdf

In the context of your posting, the main point is really how hard the
problem is to solve, even partially.  If only ICMP reply messages were
sent consistently and included the AS number of the sending router... ;)

-- Jen

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



From exim@www1.ietf.org  Wed Jul  9 17:42:36 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 RAA23761
	for <imrg-archive@odin.ietf.org>; Wed, 9 Jul 2003 17:42:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aMhV-0000Q5-Nz
	for imrg-archive@odin.ietf.org; Wed, 09 Jul 2003 17:42:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h69Lg9EO001609
	for imrg-archive@odin.ietf.org; Wed, 9 Jul 2003 17:42:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aMhV-0000Ps-KX
	for imrg-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 17:42:09 -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 RAA23725
	for <imrg-web-archive@ietf.org>; Wed, 9 Jul 2003 17:42:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aMhT-0003yW-00
	for imrg-web-archive@ietf.org; Wed, 09 Jul 2003 17:42:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19aMhS-0003yS-00
	for imrg-web-archive@ietf.org; Wed, 09 Jul 2003 17:42:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aMhN-0000Ng-C3; Wed, 09 Jul 2003 17:42:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aMhC-0000LU-2L
	for imrg@optimus.ietf.org; Wed, 09 Jul 2003 17:41:50 -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 RAA23673
	for <imrg@ietf.org>; Wed, 9 Jul 2003 17:41:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aMh8-0003x8-00
	for imrg@ietf.org; Wed, 09 Jul 2003 17:41:46 -0400
Received: from dhcp-98-125.ir.bbn.com ([192.1.98.125] helo=lawyers.ir.bbn.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19aMh7-0003x5-00
	for imrg@ietf.org; Wed, 09 Jul 2003 17:41:45 -0400
Received: by lawyers.ir.bbn.com (Postfix, from userid 9076)
	id AFA446B2B8; Wed,  9 Jul 2003 17:40:49 -0400 (EDT)
To: imrg@ietf.org
From: Mark Allman <mallman@grc.nasa.gov>
Reply-To: mallman@grc.nasa.gov
Subject: "Cottrell, Les": RE: [IMRG] Internet measurement: what next?
Organization: BBN Technologies/NASA GRC
Song-of-the-Day: Dreams
Date: Wed, 09 Jul 2003 17:40:49 -0400
Message-Id: <20030709214049.AFA446B2B8@lawyers.ir.bbn.com>
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>

 
Folks-

I asked Les to distill the high points from the slides he posted
last week (pointer in his note).  He graciously agreed and distilled
the thoughts in the attached message (which he explicitly said I
could forward to the list).

My own feeling is that there is some good stuff in these notes to
mull over and discuss.  I'd be thrilled to hear opinions.

allman


------- Forwarded Message

Date: Sat, 05 Jul 2003 10:49:14 -0700
From: "Cottrell, Les" <cottrell@SLAC.Stanford.EDU>
Subject: RE: [IMRG] Internet measurement: what next?
To: "'mallman@grc.nasa.gov'" <mallman@grc.nasa.gov>

[...]

=============================================================================
High performance networking measurement needs for Science:
Presentation to the US Interagancy Large Scale Networking (LSN) group
Les Cottrell, KC Claffy, Brian Tierney, Ronn Ritke, Nahs Wernetr Braun, June 10, 2003 
(for more details see http://www.slac.stanford.edu/grp/scs/net/talk03/lsn-jun03_files/frame.html including the notes appended to the slides)

Overview
* The end-to-end challenge, illustrations
* Solution
* End to end Monitoring Goals
* Current issues
* Problem analysis, measurement infrastructure, analysis tools, standards, collaborations
* Benefits to Science
* Consequences of not addressing issues
* Why not leave to industry
Appendix
* What is being done today
* Who is measuring?
* Who is using the measurements?
* What is being measured?
* What tools are being used?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Distributed systems are very hard
"A distributed system is one in which I can't get my work done because a computer I've never heard of has failed." Butler Lampson
When building distributed systems, we often observe unexpectedly low performance the reasons for which are usually not obvious
The bottlenecks can be in any of the following components:
* the applications
* the operating systems
* the disks, network adapters, bus, memory, etc. on either the sending or receiving host
* the network switches and routers, and so on
Problems may not be logical
* Most problems are operator errors, configurations, bugs 

Solution:
* A complete End-to-End monitoring framework that includes the following components: 
  - instrumentation tools (application, middleware, and OS monitoring) 
  - host and network sensors  (host and network monitoring)
  - sensor management  / activation tools
  - event publication service
  - event archive service
  - event analysis and visualization tools
  - a common set of protocols for describing, exchanging, and locating monitoring data
	o Need for applications (e.g. Grid middleware), diagnosis, perf. analysis
  - toolkit for streamlined problem diagnosis: detection, location, isolation & reporting 
	o glue to multiple sources of information, traceroute archives, router info, delay/loss archives, on-demand tests, baselines
	o analysis and heuristics
  - E2EPi working on solution, but only funded for coordination not for all the underlying work

End-to-end Monitoring Goals
* Have to solve the E2E performance, it is THE critical metric for user, not just a backbone bandwidth problem
* Improve end-to-end data throughput for data intensive applications in a high-speed WAN environments 
* Provide the ability to do performance analysis and fault detection in a Grid computing environment
* Provide accurate, detailed, and adaptive monitoring of all of distributed computing components, including the network
"Unfortunately, network management research has historically been very under-funded, because it is difficult to get funding bodies to recognize this as legitimate networking research," IAB Concerns & Recommendations Regarding Internet Research & Evolution

Current Issues:
1. Problem Analysis
  - Cultivate systematic studies of problems, causes, how to discover, how to report, how to by-pass
	o Analysis to help in deciding what are the most important problems, see how they are tackled manually today
	o Decide on which problems are most cost-effective to assist in developing tools to assist in diagnosis
2. Need to build infrastructures to support trouble-shooting
  - Requires repetitive and on-demand measurements with appropriate security model. 
  - Provide recommended/accepted set of tools for delay, RTT, loss, route tracking, "bandwidth" estimation. 
	o Include archiving and access to data, analysis and reporting of repetitive data. 
  - Allow for evaluation, validation and comparison of new measurement tools, TCP stacks, applications (e.g. file transfer).
  - Reverse traceroute, looking glass, remote tcpdump (e.g. SCNM), remote testing of connection (ANL NDT), 
  - Traceroute archives
  - Make tools easier to comprehend and use by scientists
  - Encourage efforts such as Internet2 E2Epi efforts to provide measurements inside the cloud
	o Extend to ESnet & other NRNs, and beyond
	o Fund collaboration across boundaries 
  - Ubiquitous coverage (require multiple toolkits): Inter agency, international, hi-speed, digital divide, long term and current
3. Analysis tools
  - Provide measurement tools to accurately & quickly identify performance problems, 
	o to automatically take action to investigate and provide information for:
		> Scientist
		> Grid support "NOC"
		> Network administrator or network person 
	o Promote well understood, accepted metrics for customers for realistic, enforceable SLAs, 
		>provide acceptable limits, 
		>provide tools to track  
4. Standards
  - All the above requires:
	o easy to use standard ways (e.g.web services) for applications to access data from existing and new monitoring projects. 
	o standard naming conventions and schemas.
  - This will provide the ability to share information from multiple measurement infrastructure projects
5. Collaboration
  - Need to build multi-disciplinary teams (incent orthogonal groups to work with one another): 
	o include people close to eventual customers (scientists, operational folks)
		> to ensure what is developed is useful, tested out in realistic environments
	o include vendors and providers in funded projects to bridge the gaps
  - E2Epi is funded to provide coordination
  - Multi agency funding!
	o This is not a problem a single agency can address
	o Science applications cross multi-agency networks, but barriers to interagency network monitoring collaborations

Benefits to Science
* Network reaches its potential
  - enable new ways of doing science: 
	o data intensive science (astrophysics, global weather, seismology, medicine), 
	o remote instrument control (SNS, fusion(ITER), surgery), 
	o remote visualization/insight (Terascale supernova, climate modeling), 
	o world-wide collaboration enabling (LHC, ITER)
  - enables scientists to do science
	o Wizard gap closure, not using all time fighting the network, rather network becomes a catalyst
  - Without good troubleshooting capabilities, the Grid vision will fail
  - Predictability, planning, expectations, raising the bar

What happnes if we do not address
* Data continues to ship inefficiently by truck/plane FedEx
  - Long delays (2 weeks), degraded collaboration, US scientists continue to lose leadership
  - Increased costs (manpower costs, lack of automation)
  - Inadequate reliability or performance for new applications, (e.g. Grid fails to reach its potential)
  -New capabilities do not emerge in US:
	o remote instrument control, real-time video, media distribution... 
	o US science loses leadership to Japan, Europe, Canada

Why no leave it to Industry
* Industry won't do it ("it's not my problem"):
* Has its interest and hands full elsewhere
* It's hard, does not sell products, little Return on Investment
* Historically poor record, competitive concerns
  - Management features are late in product development cycle
  - Early success with SNMP and Netflow
  - Commercial Network Management Platforms's (e.g. OpenView, Tivoli) limited success (network oriented, not user), not cost effective for small organizations
  - ISPs only measure own nets, not E2E, SLA guarantees are not cross-provider

------- End of Forwarded Message


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



From exim@www1.ietf.org  Wed Jul  9 18:03:33 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 SAA24556
	for <imrg-archive@odin.ietf.org>; Wed, 9 Jul 2003 18:03:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aN1n-0001ig-7P
	for imrg-archive@odin.ietf.org; Wed, 09 Jul 2003 18:03:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h69M37Ax006604
	for imrg-archive@odin.ietf.org; Wed, 9 Jul 2003 18:03:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aN1n-0001iR-3I
	for imrg-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 18:03:07 -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 SAA24506
	for <imrg-web-archive@ietf.org>; Wed, 9 Jul 2003 18:03:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aN1k-0004BH-00
	for imrg-web-archive@ietf.org; Wed, 09 Jul 2003 18:03:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19aN1j-0004BE-00
	for imrg-web-archive@ietf.org; Wed, 09 Jul 2003 18:03:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aN1h-0001gn-4R; Wed, 09 Jul 2003 18:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aN18-0001f9-Sa
	for imrg@optimus.ietf.org; Wed, 09 Jul 2003 18:02:26 -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 SAA24494
	for <imrg@ietf.org>; Wed, 9 Jul 2003 18:02:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aN16-0004B2-00
	for imrg@ietf.org; Wed, 09 Jul 2003 18:02:24 -0400
Received: from dhcp-98-125.ir.bbn.com ([192.1.98.125] helo=lawyers.ir.bbn.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19aN15-0004Az-00
	for imrg@ietf.org; Wed, 09 Jul 2003 18:02:23 -0400
Received: by lawyers.ir.bbn.com (Postfix, from userid 9076)
	id 3CD546B2B8; Wed,  9 Jul 2003 18:01:27 -0400 (EDT)
To: imrg@ietf.org
From: Mark Allman <mallman@grc.nasa.gov>
Reply-To: mallman@grc.nasa.gov
Subject: Re: [IMRG] Internet measurement: what next? 
In-Reply-To: <20030709214049.AFA446B2B8@lawyers.ir.bbn.com> 
Organization: BBN Technologies/NASA GRC
Song-of-the-Day: Dreams
Date: Wed, 09 Jul 2003 18:01:26 -0400
Message-Id: <20030709220127.3CD546B2B8@lawyers.ir.bbn.com>
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>


Les-

Les Cottrell:
> Current Issues:
> 1. Problem Analysis
>   - Cultivate systematic studies of problems, causes, how to
>     discover, how to report, how to by-pass 
> 	o Analysis to help in deciding what are the most important
> 	  problems, see how they are tackled manually today 
> 	o Decide on which problems are most cost-effective to assist
> 	  in developing tools to assist in diagnosis 

I think I have a little heartburn with this...  We **do** study
problems and report on the results.  We have papers on TCP
performance problems and BGP problems and DNS behavior and HTTP
problems and ....

So, we have all these problems sort of being worked on by various
arms of the community.  Is the real issue here that we don't have
these things pulled together in a way that folk can figure out what
has been done?  Or, are we fundementally doing things in a broken
way such that these studies are not Good Enough?

> 2. Need to build infrastructures to support trouble-shooting
>   - Requires repetitive and on-demand measurements with
>     appropriate security model. 

Right on.

>   - Provide recommended/accepted set of tools for delay, RTT,
>     loss, route tracking, "bandwidth" estimation.  

Do we know what these tools are?  I.e., is really all that needs
done is to write something that says "thou shalt use these things to
facilitate comparisons"?  Or, are we still struggling with figuring
some or all of the above out?  (I.e., it seems to me that we have
not reached consensus on "bandwidth estimation".  Or, have we?)

> 	o Include archiving and access to data, analysis and
> 	  reporting of repetitive data.  

Yes.

>   - Allow for evaluation, validation and comparison of new
>     measurement tools, TCP stacks, applications (e.g. file
>     transfer).

What do you envision?  This is really hard, right?  Validating a
tool that maps the topology (for instance) is quite hard, right?  We
have lots of techniques that we all admit have weaknesses.  So, what
do we validate against?  What is the approach here?

Or, how do I validate a new TCP stack?  There is such hetrogeneity
in TCP implemenations these days (even between linux versions!),
what can we compare to as "the truth"?  

(I realize this was a plea for an infusion of US government $$$,
but...) 

> Why no leave it to Industry
> * Industry won't do it ("it's not my problem"):
> * Has its interest and hands full elsewhere
> * It's hard, does not sell products, little Return on Investment
> * Historically poor record, competitive concerns
>   - Management features are late in product development cycle
>   - Early success with SNMP and Netflow
>   - Commercial Network Management Platforms's (e.g. OpenView,
>     Tivoli) limited success (network oriented, not user), not cost
>     effective for small organizations 
>   - ISPs only measure own nets, not E2E, SLA guarantees are not
>     cross-provider 

This doesn't seem right to me.  Some industry has a vested
interest and has demonstrated that with contributions to this field,
I believe.  Providers (no matter size), for instance, surely want to
be able to measure their networks to improve performance.  Companies
that serve web pages no doubt want to do it faster than their
competitors and would like to be able to get some good data on such
things.  Etc.  Etc.  Etc.

Plus, in your list you are noting that you need more visibility into
the middle of the network.  I don't doubt that.  However, that is
going to take a partnership with industry at a minimum, right?

I am certainly not claiming that industry is going to solve all the
problems.  On the other hand, I think that they have and will likely
continue to play a valuable and needed role.  Right?

Thanks!

allman


--
Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/

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



From exim@www1.ietf.org  Thu Jul 10 20:40:34 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 UAA28118
	for <imrg-archive@odin.ietf.org>; Thu, 10 Jul 2003 20:40:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19alxI-0000J7-CO
	for imrg-archive@odin.ietf.org; Thu, 10 Jul 2003 20:40:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B0e8M4001175
	for imrg-archive@odin.ietf.org; Thu, 10 Jul 2003 20:40:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19alxI-0000Is-0p
	for imrg-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 20:40:08 -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 UAA28104
	for <imrg-web-archive@ietf.org>; Thu, 10 Jul 2003 20:40:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19alxF-0000lp-00
	for imrg-web-archive@ietf.org; Thu, 10 Jul 2003 20:40:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19alxF-0000lm-00
	for imrg-web-archive@ietf.org; Thu, 10 Jul 2003 20:40:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19alxA-0000Gr-UF; Thu, 10 Jul 2003 20:40:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19alwe-0000G1-9D
	for imrg@optimus.ietf.org; Thu, 10 Jul 2003 20:39:28 -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 UAA28087
	for <imrg@irtf.org>; Thu, 10 Jul 2003 20:39:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19alwc-0000lX-00
	for imrg@irtf.org; Thu, 10 Jul 2003 20:39:26 -0400
Received: from jaguar.icir.org ([192.150.187.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 19alwb-0000lT-00
	for imrg@irtf.org; Thu, 10 Jul 2003 20:39:25 -0400
Received: from jaguar.icir.org (localhost [127.0.0.1])
	by jaguar.icir.org (8.12.8p1/8.12.3) with ESMTP id h6B0dOw9009622
	for <imrg@irtf.org>; Thu, 10 Jul 2003 17:39:25 -0700 (PDT)
	(envelope-from vern@jaguar.icir.org)
Message-Id: <200307110039.h6B0dOw9009622@jaguar.icir.org>
To: imrg@irtf.org
Date: Thu, 10 Jul 2003 17:39:24 -0700
From: Vern Paxson <vern@icir.org>
Subject: [IMRG] test - please ignore
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>


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



From exim@www1.ietf.org  Mon Jul 14 14:40:09 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 OAA12864
	for <imrg-archive@odin.ietf.org>; Mon, 14 Jul 2003 14:40:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19c8Eg-0000kg-30
	for imrg-archive@odin.ietf.org; Mon, 14 Jul 2003 14:39:42 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6EIdgRT002885
	for imrg-archive@odin.ietf.org; Mon, 14 Jul 2003 14:39:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19c8Ef-0000kS-VC
	for imrg-web-archive@optimus.ietf.org; Mon, 14 Jul 2003 14:39:41 -0400
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 OAA12802
	for <imrg-web-archive@ietf.org>; Mon, 14 Jul 2003 14:39:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19c8E1-0000eO-Kh; Mon, 14 Jul 2003 14:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19c8DG-0000dG-8X
	for imrg@optimus.ietf.org; Mon, 14 Jul 2003 14:38:14 -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 OAA12686
	for <imrg@ietf.org>; Mon, 14 Jul 2003 14:38:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c8DC-00053J-00
	for imrg@ietf.org; Mon, 14 Jul 2003 14:38:10 -0400
Received: from smtp.slac.stanford.edu ([134.79.18.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c8DB-00053D-00
	for imrg@ietf.org; Mon, 14 Jul 2003 14:38:09 -0400
Received: from CONVERSION-DAEMON.smtp.slac.stanford.edu by
 smtp.slac.stanford.edu (PMDF V6.1-1 #37665)
 id <0HI100J012FBML@smtp.slac.stanford.edu> for imrg@ietf.org; Mon,
 14 Jul 2003 11:38:00 -0700 (PDT)
Received: from smtpserv1.slac.stanford.edu
 (smtpserv1.slac.stanford.edu [134.79.18.81]) by smtp.slac.stanford.edu
 (PMDF V6.1-1 #37665) with ESMTP id <0HI100GOZ2FB8E@smtp.slac.stanford.edu>;
 Mon, 14 Jul 2003 11:37:59 -0700 (PDT)
Received: from ATREUS.win.slac.stanford.edu ([134.79.16.83])
 by smtpserv1.slac.stanford.edu (PMDF V6.1-1 #37665)
 with ESMTP id <0HI10084K2FBVT@smtpserv1.slac.stanford.edu>; Mon,
 14 Jul 2003 11:37:59 -0700 (PDT)
Received: by atreus.slac.stanford.edu with Internet Mail Service (5.5.2653.19)
	id <N1LMG9C2>; Mon, 14 Jul 2003 11:37:57 -0700
Content-return: allowed
Date: Mon, 14 Jul 2003 11:37:52 -0700
From: "Cottrell, Les" <cottrell@SLAC.Stanford.EDU>
Subject: RE: [IMRG] Internet measurement: what next?
To: "'mallman@grc.nasa.gov'" <mallman@grc.nasa.gov>,
        "'imrg@ietf.org'" <imrg@ietf.org>
Message-id: 
 <2846497B437BF84BAD1A4CC407418D2603063046@exchange1.slac.stanford.edu>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: text/plain
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Mark: Thanks for the comments.

> Les Cottrell:
> > Current Issues:
> > 1. Problem Analysis
> >   - Cultivate systematic studies of problems, causes, how to
> >     discover, how to report, how to by-pass 
> > 	o Analysis to help in deciding what are the most important
> > 	  problems, see how they are tackled manually today 
> > 	o Decide on which problems are most cost-effective to assist
> > 	  in developing tools to assist in diagnosis
> 
> I think I have a little heartburn with this...  We **do** 
> study problems and report on the results.  We have papers on 
> TCP performance problems and BGP problems and DNS behavior 
> and HTTP problems and ....
> 
> So, we have all these problems sort of being worked on by 
> various arms of the community.  Is the real issue here that 
> we don't have these things pulled together in a way that folk 
> can figure out what has been done?  Or, are we fundementally 
> doing things in a broken way such that these studies are not 
> Good Enough?
This was in response to concerns raised by Vern Paxson and others, see for example: Vern's talk Aug2001 www.icir.org/vern/talks/vp-nrdm01.ps.gz and also see David Moore's talk http://www.caida.org/outreach/presentations/2002/ipam0203/ipam0203.pdf. Kc felt strongly that we needed to make a point of this. Your points are correct there is a bit of both. 
 
> >   - Provide recommended/accepted set of tools for delay, RTT,
> >     loss, route tracking, "bandwidth" estimation.
> 
> Do we know what these tools are?  I.e., is really all that 
> needs done is to write something that says "thou shalt use 
> these things to facilitate comparisons"?  Or, are we still 
> struggling with figuring some or all of the above out?  
> (I.e., it seems to me that we have not reached consensus on 
> "bandwidth estimation".  Or, have we?)
In some cases (e.g. loss & delay) the tools are reasonably well known (though there are problems about whether say ping measures the same losses or RTT as seen by TCP), in other cases (bandwidth estimation) the jury is still out and there are multiple tools that measure different things (available bandwidth, bottleneck capacity, achievable bandwidth etc.) and how they relate to one another is not fully understood, and in some cases (packet pair & train methods) may not work well at higher speeds with advanced ToE NICs. 

> >   - Allow for evaluation, validation and comparison of new
> >     measurement tools, TCP stacks, applications (e.g. file
> >     transfer).
> 
> What do you envision?  This is really hard, right?  
> Validating a tool that maps the topology (for instance) is 
> quite hard, right?  We have lots of techniques that we all 
> admit have weaknesses.  So, what do we validate against?  
> What is the approach here?
> 
> Or, how do I validate a new TCP stack?  There is such 
> hetrogeneity in TCP implemenations these days (even between 
> linux versions!), what can we compare to as "the truth"?  
> 
> (I realize this was a plea for an infusion of US government $$$,
> but...) 
You are right this IS really hard.  There are few if any absolute "truths" today.
For tools I was thinking to compare tools (e.g. iperf vs. pathload vs GridFTP vs say BW=a*MSS/(RTT*sqrt(loss)) to understand the regions of applicability, how well one can use one to deduce another (e.g. a lightweight measure (ping or pathload) to predict what a heavier weight measurement (say iperf or GridFTP) might see). In the case of capacity there may be something close to truth to validate against. Possibly if we had instantaneous utilizations of all network devices alonmg a path we might be able to validate some of the available bandwidth tools. I have not thought about topology.
For TCP stacks, applications and users want the best throughput, with the easiest way to use (e.g. do not have to optimize both number of parallel streams AND max window size), the best predictability, plus a feeling they are not being grossly unfair to others.  Networkers will put more emphasis on fairness, and maybe agility etc. There is currently no absolute "truth".
 
> > Why not leave it to Industry
> > * Industry won't do it ("it's not my problem"):
> > * Has its interest and hands full elsewhere
> > * It's hard, does not sell products, little Return on Investment
> > * Historically poor record, competitive concerns
> >   - Management features are late in product development cycle
> >   - Early success with SNMP and Netflow
> >   - Commercial Network Management Platforms's (e.g. OpenView,
> >     Tivoli) limited success (network oriented, not user), not cost
> >     effective for small organizations 
> >   - ISPs only measure own nets, not E2E, SLA guarantees are not
> >     cross-provider
> 
> This doesn't seem right to me.  Some industry has a vested 
> interest and has demonstrated that with contributions to this 
> field, I believe.  Providers (no matter size), for instance, 
> surely want to be able to measure their networks to improve 
> performance.  Companies that serve web pages no doubt want to 
> do it faster than their competitors and would like to be able 
> to get some good data on such things.  Etc.  Etc.  Etc.
You are right providers such as Sprint and AT&T want to measure their 
own networks ("you can't manage what you don't measure"), however for the end-users this does not provide end-to-end performance expectations.
As you say web services companies ought to be interested in this in order to provide better customer service. However there does not appear to be much out there are the moment, it's mainly traffic light red/yellow/green

> Plus, in your list you are noting that you need more 
> visibility into the middle of the network.  I don't doubt 
> that.  However, that is going to take a partnership with 
> industry at a minimum, right?
Right on. We need to engage industry to provide this visibility. Currently this is pretty limited. One way to make a start on this would be to engage the Academic & Research networks (e.g. Internet2, Esnet, GEANT, ...). From this an understanding of what is useful, and how to provide access (publicize and subscribe, standard naming etc.)could emerge. Internet2 seems to be particularly interested in this. However, it is still a long step to having the information available from industry at large.  

> I am certainly not claiming that industry is going to solve 
> all the problems.  On the other hand, I think that they have 
> and will likely continue to play a valuable and needed role. Right?
Right.

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



From exim@www1.ietf.org  Tue Jul 15 07:16:17 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 HAA14229
	for <imrg-archive@odin.ietf.org>; Tue, 15 Jul 2003 07:16:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cNmf-00080k-OS
	for imrg-archive@odin.ietf.org; Tue, 15 Jul 2003 07:15:49 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6FBFngU030790
	for imrg-archive@odin.ietf.org; Tue, 15 Jul 2003 07:15:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cNmf-00080X-Kr
	for imrg-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 07:15:49 -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 HAA14219
	for <imrg-web-archive@ietf.org>; Tue, 15 Jul 2003 07:15:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cNma-0000k0-00
	for imrg-web-archive@ietf.org; Tue, 15 Jul 2003 07:15:44 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cNmA-0000jo-00
	for imrg-web-archive@ietf.org; Tue, 15 Jul 2003 07:15:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cNlt-0007wB-3v; Tue, 15 Jul 2003 07:15:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cNkw-0007vF-3S
	for imrg@optimus.ietf.org; Tue, 15 Jul 2003 07:14: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 HAA14177
	for <imrg@ietf.org>; Tue, 15 Jul 2003 07:13:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cNkq-0000j5-00
	for imrg@ietf.org; Tue, 15 Jul 2003 07:13:56 -0400
Received: from kc-msxproto2.kc.umkc.edu ([134.193.143.159])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cNkL-0000iu-00
	for imrg@ietf.org; Tue, 15 Jul 2003 07:13:25 -0400
Received: from monk ([134.193.6.66]) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 15 Jul 2003 06:12:35 -0500
Message-ID: <001301c34ac1$fe3733c0$4206c186@monk>
From: "Amit Sinha" <asinha@conrel.sice.umkc.edu>
To: <imrg@ietf.org>
Date: Tue, 15 Jul 2003 06:12:34 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0010_01C34A98.154EDC40"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 15 Jul 2003 11:12:35.0399 (UTC) FILETIME=[FE69B570:01C34AC1]
Subject: [IMRG] Network measurement in Private Network
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0010_01C34A98.154EDC40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello all,

Is there any work that analyze a Private Network based on traffic =
measurement?
How significantly does the utilization differ from a Public Network?
Is there any research paper/white paper that I can refer to related to =
this topic?

Thanks for your time and help.

Regards,
Amit
------=_NextPart_000_0010_01C34A98.154EDC40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello all,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Is there any work&nbsp;that analyze a =
Private=20
Network based on traffic measurement?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>How significantly does the utilization =
differ from=20
a Public Network?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Is there any research paper/white paper =
that I can=20
refer to related to this topic?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks for your time and =
help.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Amit</FONT></DIV></BODY></HTML>

------=_NextPart_000_0010_01C34A98.154EDC40--


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



From exim@www1.ietf.org  Wed Jul 16 11:07:49 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 LAA05339
	for <imrg-archive@odin.ietf.org>; Wed, 16 Jul 2003 11:07:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnsI-0000UF-8X
	for imrg-archive@odin.ietf.org; Wed, 16 Jul 2003 11:07:24 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GF7M1m001865
	for imrg-archive@odin.ietf.org; Wed, 16 Jul 2003 11:07:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnsI-0000U0-3q
	for imrg-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 11:07:22 -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 LAA05325
	for <imrg-web-archive@ietf.org>; Wed, 16 Jul 2003 11:07:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cnsF-0000KK-00
	for imrg-web-archive@ietf.org; Wed, 16 Jul 2003 11:07:19 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cns9-0000KG-00
	for imrg-web-archive@ietf.org; Wed, 16 Jul 2003 11:07:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnrx-0000Kt-GE; Wed, 16 Jul 2003 11:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnrN-0000K3-EJ
	for imrg@optimus.ietf.org; Wed, 16 Jul 2003 11:06:25 -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 LAA05300
	for <imrg@ietf.org>; Wed, 16 Jul 2003 11:06:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cnrK-0000JQ-00
	for imrg@ietf.org; Wed, 16 Jul 2003 11:06:22 -0400
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cnr4-0000Is-00
	for imrg@ietf.org; Wed, 16 Jul 2003 11:06:07 -0400
Received: from magnum.cs.columbia.edu (IDENT:root@magnum.cs.columbia.edu [128.59.16.117])
	by cs.columbia.edu (8.12.9/8.12.9) with ESMTP id h6GF4LkM018709
	for <imrg@ietf.org>; Wed, 16 Jul 2003 11:04:21 -0400 (EDT)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by magnum.cs.columbia.edu (8.11.6/8.9.3) with ESMTP id h6GF4Kg04955
	for <imrg@ietf.org>; Wed, 16 Jul 2003 11:04:21 -0400
Message-ID: <3F15687D.1070402@cs.columbia.edu>
Date: Wed, 16 Jul 2003 11:00:13 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: imrg@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [IMRG] Web retrieval logs with referrer information
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

We're looking for reasonably recent web server logs with referrer 
information, particularly for internal traversals.

Thank you.

Henning Schulzrinne


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



From exim@www1.ietf.org  Sat Jul 19 18:25:45 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 SAA24989
	for <imrg-archive@odin.ietf.org>; Sat, 19 Jul 2003 18:25:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19e08m-0004KC-IS
	for imrg-archive@odin.ietf.org; Sat, 19 Jul 2003 18:25:20 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6JMPKpZ016618
	for imrg-archive@odin.ietf.org; Sat, 19 Jul 2003 18:25:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19e08m-0004Jx-4R
	for imrg-web-archive@optimus.ietf.org; Sat, 19 Jul 2003 18:25:20 -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 SAA24968
	for <imrg-web-archive@ietf.org>; Sat, 19 Jul 2003 18:25:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19e08j-0004jA-00
	for imrg-web-archive@ietf.org; Sat, 19 Jul 2003 18:25:17 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19e08d-0004j6-00
	for imrg-web-archive@ietf.org; Sat, 19 Jul 2003 18:25:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19e08T-0004HL-9D; Sat, 19 Jul 2003 18:25:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19e07t-0004H3-Ji
	for imrg@optimus.ietf.org; Sat, 19 Jul 2003 18:24:25 -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 SAA24965
	for <imrg@ietf.org>; Sat, 19 Jul 2003 18:24:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19e07q-0004iV-00
	for imrg@ietf.org; Sat, 19 Jul 2003 18:24:22 -0400
Received: from mail.npd.ufsc.br ([150.162.2.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19e07f-0004iK-00
	for imrg@ietf.org; Sat, 19 Jul 2003 18:24:12 -0400
Received: from localhost (localhost [127.0.0.1])
	by mail.npd.ufsc.br (Postfix) with ESMTP id 58EFD77E
	for <imrg@ietf.org>; Sat, 19 Jul 2003 19:28:31 -0300 (BRT)
Received: by mail.npd.ufsc.br (Postfix, from userid 1013)
	id AF4D9776; Sat, 19 Jul 2003 19:28:30 -0300 (BRT)
Received: from localhost (localhost [127.0.0.1])
	by mail.npd.ufsc.br (Postfix) with ESMTP id AA4DB772
	for <imrg@ietf.org>; Sat, 19 Jul 2003 19:28:30 -0300 (BRT)
Date: Sat, 19 Jul 2003 19:28:30 -0300 (BRT)
From: Augusto Castelan Carlson <carlson@npd.ufsc.br>
To: imrg@ietf.org
Message-ID: <Pine.LNX.4.44.0307191928020.8163-100000@mail.npd.ufsc.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS 0.3.12pre8
Subject: [IMRG] clock synchronization
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>

Hi!

Is there advantages in use GPS clock synchronization for network
measurements?
If so, which GPS product is recommended for it?

Thank you!

--
Augusto Castelan Carlson


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



From exim@www1.ietf.org  Sat Jul 19 23:26:38 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 XAA28377
	for <imrg-archive@odin.ietf.org>; Sat, 19 Jul 2003 23:26:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19e4pw-0001dz-8l
	for imrg-archive@odin.ietf.org; Sat, 19 Jul 2003 23:26:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6K3QCt4006313
	for imrg-archive@odin.ietf.org; Sat, 19 Jul 2003 23:26:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19e4pw-0001dk-1d
	for imrg-web-archive@optimus.ietf.org; Sat, 19 Jul 2003 23:26:12 -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 XAA28374
	for <imrg-web-archive@ietf.org>; Sat, 19 Jul 2003 23:26:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19e4pu-0006GY-00
	for imrg-web-archive@ietf.org; Sat, 19 Jul 2003 23:26:10 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19e4po-0006GV-00
	for imrg-web-archive@ietf.org; Sat, 19 Jul 2003 23:26:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19e4pl-0001cE-9d; Sat, 19 Jul 2003 23:26:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19e4pi-0001c0-7P
	for imrg@optimus.ietf.org; Sat, 19 Jul 2003 23:25:58 -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 XAA28371
	for <imrg@ietf.org>; Sat, 19 Jul 2003 23:25:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19e4pg-0006GP-00
	for imrg@ietf.org; Sat, 19 Jul 2003 23:25:56 -0400
Received: from kc-msxproto2.kc.umkc.edu ([134.193.143.159])
	by ietf-mx with esmtp (Exim 4.12)
	id 19e4pV-0006GG-00
	for imrg@ietf.org; Sat, 19 Jul 2003 23:25:45 -0400
Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Sat, 19 Jul 2003 22:25:21 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [IMRG] clock synchronization
Date: Sat, 19 Jul 2003 22:25:20 -0500
Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B0110803D@KC-MAIL4.kc.umkc.edu>
Thread-Topic: [IMRG] clock synchronization
Thread-Index: AcNORJm+2xRGbtt8SNS1saz+y57z/wAJpTew
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Augusto Castelan Carlson" <carlson@npd.ufsc.br>, <imrg@ietf.org>
X-OriginalArrivalTime: 20 Jul 2003 03:25:21.0035 (UTC) FILETIME=[8CB1FDB0:01C34E6E]
Content-Transfer-Encoding: quoted-printable
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable



> Is there advantages in use GPS clock synchronization for network
> measurements?

 time stamps play a crucial role in the probing based measurement=20
 studies. Possibly, RIPE-NCC test traffic will give an idea about=20
 its importance.=20


 Also, you should read=20

   PC Based Precision Timing Without GPS=20
   Attila Pasztor, Darryl Veitch=20
   http://parapet.ee.princeton.edu/~sigm2002/papers/p1-pasztor.pdf

 and check Darryl Veitch/David Mills website for more details.



 The related advantage of GPS can be inferred from the ranking of=20
 the timing accuracy as below (as per my understanding of the
 above paper; i may be wrong):

    o software clock + NTP=20
    o GPS based
    o TSC + driver timestamp =20
    o RT-TSC + driver timestamp
    o GPS sync DAG + TSC + driver timestamp
    o ???

 I have no clue about the cost factors which plays an important
 role.=20



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



From exim@www1.ietf.org  Mon Jul 21 04:02:45 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 EAA20578
	for <imrg-archive@odin.ietf.org>; Mon, 21 Jul 2003 04:02:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19eVcg-00030t-Vw
	for imrg-archive@odin.ietf.org; Mon, 21 Jul 2003 04:02:19 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6L82IMs011582
	for imrg-archive@odin.ietf.org; Mon, 21 Jul 2003 04:02:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19eVcg-00030j-NT
	for imrg-web-archive@optimus.ietf.org; Mon, 21 Jul 2003 04:02:18 -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 EAA20575
	for <imrg-web-archive@ietf.org>; Mon, 21 Jul 2003 04:02:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eVce-0000nr-00
	for imrg-web-archive@ietf.org; Mon, 21 Jul 2003 04:02:16 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19eVcY-0000no-00
	for imrg-web-archive@ietf.org; Mon, 21 Jul 2003 04:02:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19eVcP-0002tR-RV; Mon, 21 Jul 2003 04:02:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19eVc7-0002sh-JH
	for imrg@optimus.ietf.org; Mon, 21 Jul 2003 04:01:43 -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 EAA20569
	for <imrg@ietf.org>; Mon, 21 Jul 2003 04:01:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eVc4-0000nV-00
	for imrg@ietf.org; Mon, 21 Jul 2003 04:01:40 -0400
Received: from birch.ripe.net ([193.0.1.96])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eVbt-0000nF-00
	for imrg@ietf.org; Mon, 21 Jul 2003 04:01:29 -0400
Received: from x49.ripe.net (x49.ripe.net [193.0.1.49])
	by birch.ripe.net (8.12.9/8.11.6) with ESMTP id h6L80YNe001390;
	Mon, 21 Jul 2003 10:00:34 +0200
Received: from localhost (henk@localhost)
	by x49.ripe.net (8.12.9/8.12.6) with ESMTP id h6L80XtA017403;
	Mon, 21 Jul 2003 10:00:34 +0200
X-Authentication-Warning: x49.ripe.net: henk owned process doing -bs
Date: Mon, 21 Jul 2003 10:00:33 +0200 (CEST)
From: "Henk Uijterwaal (RIPE-NCC)" <henk@ripe.net>
To: Augusto Castelan Carlson <carlson@npd.ufsc.br>
cc: imrg@ietf.org
Subject: Re: [IMRG] clock synchronization
In-Reply-To: <Pine.LNX.4.44.0307191928020.8163-100000@mail.npd.ufsc.br>
Message-ID: <Pine.LNX.4.44.0307210949100.17006-100000@x49.ripe.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>

Hi,

> Is there advantages in use GPS clock synchronization for network
> measurements?

Clock synchronization is essential for one way measurements that involve
timing.  The most obvious is one way delay: one box sending packets, the
other one receiving it, if the clocks aren't synchronized then it is
impossible to do these measurements.

There are many ways to synchronize a clock: over the network using NTP or
from an outside source (GPS, CDMA, DCF77 and other long-wave radio clocks,
atomic clocks).

NTP suffers from the problem that it often uses the same network to
synchronize the clocks and do the measurement.  That unfortunately means
that clock accuracy goes down when the network behaves badly (losses,
delay variations) and this is usually the time that you are interested in
accurate measurements.

The advantage of GPS over other solutions is that it works everywhere _if
you can see the sky_.  Units are relatively cheap (500-1000 US$).  CDMA is
a good alternative if you live in an area with CDMA coverage.

> If so, which GPS product is recommended for it?

That depends on several factors.  In theory, any GPS receiver that can
output a pulse-per-second (clock pulse) can be used to sync a clock. In
practice, things like distance between receiver and antenna, availability
of drivers for receiver and O/S, are also important.

Henk


------------------------------------------------------------------------------
Henk Uijterwaal                             Email: henk.uijterwaal@ripe.net
RIPE Network Coordination Centre            WWW: http://www.ripe.net/home/henk
P.O.Box 10096          Singel 258           Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam    Fax: +31.20.5354445
The Netherlands        The Netherlands      Mobile: +31.6.55861746
------------------------------------------------------------------------------

That problem that we weren't having yesterday, is it better? (Big ISP NOC)








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



From exim@www1.ietf.org  Mon Jul 21 14:22:44 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 OAA05747
	for <imrg-archive@odin.ietf.org>; Mon, 21 Jul 2003 14:22:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19efIg-0007eK-Cs
	for imrg-archive@odin.ietf.org; Mon, 21 Jul 2003 14:22:18 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6LIMIq7029392
	for imrg-archive@odin.ietf.org; Mon, 21 Jul 2003 14:22:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19efIg-0007df-7r
	for imrg-web-archive@optimus.ietf.org; Mon, 21 Jul 2003 14:22:18 -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 OAA05744
	for <imrg-web-archive@ietf.org>; Mon, 21 Jul 2003 14:22:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19efId-0005BP-00
	for imrg-web-archive@ietf.org; Mon, 21 Jul 2003 14:22:15 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19efIY-0005BK-00
	for imrg-web-archive@ietf.org; Mon, 21 Jul 2003 14:22:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19efIO-0007a9-Qy; Mon, 21 Jul 2003 14:22:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ef6n-0007I2-2v
	for imrg@optimus.ietf.org; Mon, 21 Jul 2003 14:10:01 -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 OAA05587
	for <IMRG@ietf.org>; Mon, 21 Jul 2003 14:09:56 -0400 (EDT)
From: john_eidson@agilent.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ef6k-00055u-00
	for IMRG@ietf.org; Mon, 21 Jul 2003 14:09:58 -0400
Received: from tripod-ext.labs.agilent.com ([192.25.140.133] helo=tripod-int.labs.agilent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ef6Z-00055h-00
	for IMRG@ietf.org; Mon, 21 Jul 2003 14:09:48 -0400
Received: from thing2.labs.agilent.com (thing2.labs.agilent.com [130.29.252.19])
	by tripod-int.labs.agilent.com (8.12.9/8.12.9/Tripod Sendmail Config v01.02 2002/09/24) with ESMTP id h6LI8mnV005968
	for <IMRG@ietf.org>; Mon, 21 Jul 2003 11:08:48 -0700
Received: from alexbh1.labs.agilent.com (alexbh1.labs.agilent.com [130.29.252.76])
	by thing2.labs.agilent.com (8.12.9/8.12.9/Agilent Labs Mail Hub v 01.02 2002/02/06) with SMTP id h6LI8ltq003758
	for <IMRG@ietf.org>; Mon, 21 Jul 2003 11:08:47 -0700
Received: from 130.29.252.19 by alexbh1.labs.agilent.com (InterScan E-Mail VirusWall NT); Mon, 21 Jul 2003 11:08:47 -0700
Received: from alex2.labs.agilent.com (alex2.labs.agilent.com [130.29.252.56])
	by thing2.labs.agilent.com (8.12.9/8.12.9/Agilent Labs Mail Hub v 01.02 2002/02/06) with ESMTP id h6LI8jEr003744
	for <IMRG@ietf.org>; Mon, 21 Jul 2003 11:08:45 -0700
Received: by ALEX2 with Internet Mail Service (5.5.2656.59)
	id <PHMW9YQJ>; Mon, 21 Jul 2003 11:08:45 -0700
Message-ID: <FC0B9DA2600ED4118F76009027AA5DDD07E77791@ALEX2>
To: IMRG@ietf.org
Subject: FW: [IMRG] clock synchronization
Date: Mon, 21 Jul 2003 11:08:42 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-102.4 required=5.0
	tests=BAYES_20,NO_REAL_NAME,ORIGINAL_MESSAGE,QUOTED_EMAIL_TEXT,
	      USER_IN_WHITELIST
	version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
Sender: imrg-admin@ietf.org
Errors-To: imrg-admin@ietf.org
X-BeenThere: imrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=unsubscribe>
List-Id: Internet Measurement Research Group <imrg.ietf.org>
List-Post: <mailto:imrg@ietf.org>
List-Help: <mailto:imrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imrg>,
	<mailto:imrg-request@ietf.org?subject=subscribe>

To all:
I was copied on the message below. You may be interested in IEEE 1588, a new standard for synchronizing clocks in relatively compact systems (a few subnets). The standard was targeted at test and measurement, industrial control, etc but there has been some interest from the telecommunications industry. (see the tentative workshop program on the 1588 website). Further information on IEEE 1588 may be found at the website http://ieee1588.nist.gov 

regards,
john eidson
chair IEEE 1588 working group


-----Original Message-----
From: 	Henk Uijterwaal (RIPE-NCC) [mailto:henk@ripe.net] 
Sent:	Monday, July 21, 2003 1:01 AM
To:	Augusto Castelan Carlson
Cc:	imrg@ietf.org
Subject:	Re: [IMRG] clock synchronization

Hi,

> Is there advantages in use GPS clock synchronization for network
> measurements?

Clock synchronization is essential for one way measurements that involve timing.  The most obvious is one way delay: one box sending packets, the other one receiving it, if the clocks aren't synchronized then it is impossible to do these measurements.
There are many ways to synchronize a clock: over the network using NTP or from an outside source (GPS, CDMA, DCF77 and other long-wave radio clocks, atomic clocks).
NTP suffers from the problem that it often uses the same network to synchronize the clocks and do the measurement.  That unfortunately means that clock accuracy goes down when the network behaves badly (losses, delay variations) and this is usually the time that you are interested in accurate measurements.
The advantage of GPS over other solutions is that it works everywhere _if you can see the sky_.  Units are relatively cheap (500-1000 US$).  CDMA is a good alternative if you live in an area with CDMA coverage.
> If so, which GPS product is recommended for it?

That depends on several factors.  In theory, any GPS receiver that can output a pulse-per-second (clock pulse) can be used to sync a clock. In practice, things like distance between receiver and antenna, availability of drivers for receiver and O/S, are also important.
Henk

------------------------------------------------------------------------------
Henk Uijterwaal                             Email: henk.uijterwaal@ripe.net
RIPE Network Coordination Centre            WWW: http://www.ripe.net/home/henk
P.O.Box 10096          Singel 258           Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam    Fax: +31.20.5354445
The Netherlands        The Netherlands      Mobile: +31.6.55861746
------------------------------------------------------------------------------

That problem that we weren't having yesterday, is it better? (Big ISP NOC)







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

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



