
From iesg-secretary@ietf.org  Fri Sep  3 10:11:23 2010
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4619D3A6950; Fri,  3 Sep 2010 10:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.545
X-Spam-Level: 
X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jNllpq+n6xX7; Fri,  3 Sep 2010 10:11:21 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 195B03A6955; Fri,  3 Sep 2010 10:11:19 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
Message-ID: <20100903171119.28915.19909.idtracker@localhost>
Date: Fri, 03 Sep 2010 10:11:19 -0700
Cc: Internet Architecture Board <iab@iab.org>, ippm chair <ippm-chairs@tools.ietf.org>, ippm mailing list <ippm@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [ippm] Protocol Action: 'Spatial Composition of Metrics' to Proposed Standard
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Sep 2010 17:11:23 -0000

The IESG has approved the following document:
- 'Spatial Composition of Metrics'
  <draft-ietf-ippm-spatial-composition-16.txt> as a Proposed Standard

This document is the product of the IP Performance Metrics Working Group.

The IESG contact person is Lars Eggert.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-ippm-spatial-composition/



Technical Summary
 
This memo utilizes IP Performance Metrics that are applicable to both
complete paths and sub-paths, and defines relationships to compose a
complete path metric from the sub-path metrics with some accuracy
w.r.t. the actual metrics. This is called Spatial Composition in RFC
2330. The memo refers to the Framework for Metric Composition, and
provides background and motivation for combining metrics to derive
others. The descriptions of several composed metrics and statistics
follow.
 
Working Group Summary
 
The normal WG process was followed and the document has been discussed for
several years. The document as it is now, reflects WG consensus, with
nothing special worth noticing.
 
Personnel

Henk Uijterwaal (henk@ripe.net) is the document shepherd. Lars Eggert
(lars.eggert@nokia.com) reviewed the document for the IESG.

From Barry.Constantine@jdsu.com  Fri Sep  3 11:08:45 2010
Return-Path: <Barry.Constantine@jdsu.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 364033A6950 for <ippm@core3.amsl.com>; Fri,  3 Sep 2010 11:08:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.955
X-Spam-Level: 
X-Spam-Status: No, score=-5.955 tagged_above=-999 required=5 tests=[AWL=0.644,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YkNidx3SufW0 for <ippm@core3.amsl.com>; Fri,  3 Sep 2010 11:08:43 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by core3.amsl.com (Postfix) with SMTP id 90E333A690D for <ippm@ietf.org>; Fri,  3 Sep 2010 11:08:42 -0700 (PDT)
Received: from source ([209.36.247.244]) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKTIE5xTe5yFcHi3AMwfsqS4dYKpukmeWO@postini.com; Fri, 03 Sep 2010 11:09:13 PDT
Received: from milexhtca2.ds.jdsu.net ([10.75.2.122]) by Outbound1.jdsu.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 3 Sep 2010 11:07:36 -0700
Received: from MILEXCH1.ds.jdsu.net ([fe80::6444:f010:6d40:bdb]) by milexhtca2.ds.jdsu.net ([::1]) with mapi; Fri, 3 Sep 2010 11:07:35 -0700
From: Barry Constantine <Barry.Constantine@jdsu.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>, "henk@ripe.net" <henk@ripe.net>
Date: Fri, 3 Sep 2010 11:07:33 -0700
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
Thread-Index: ActI5hDf36OqIEzkTBesOmMMqCSfmwABnUUgAJsBURA=
Message-ID: <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net>
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de>
In-Reply-To: <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Sep 2010 18:07:36.0765 (UTC) FILETIME=[E3B2DED0:01CB4B92]
Cc: "ippm@ietf.org" <ippm@ietf.org>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Sep 2010 18:08:45 -0000

Hello Rudi,

I think your suggestion is reasonable.

Never hurts to be explicit, so we will add Framework to the title as you me=
ntioned.

We'll title it:  "Framework for TCP Throughput Testing" and add some refere=
nce to framework in the intro.

Thanks again,

Barry

=20

Principal Member of Technical Staff

=20

JDSU Communication Test (formerly Acterna)

Emerging Markets and Technology Research        =20

One Milestone Center Court                             =20

Germantown, MD 20876                                        =20

(W) 240-404-2227                                               =20

(C) 301-325-7069

-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of Rue=
diger.Geib@telekom.de
Sent: Tuesday, August 31, 2010 5:51 AM
To: henk@ripe.net
Cc: ippm@ietf.org
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Henk,

If time allows, I'll send more comments.

If not, here's my view:

Change the document title to

"Framework for a TCP Throughput Testing Methodology"


Arguments:

The document as is does not contain any Type P Specification. See definitio=
ns in

"2.2 Metrics for TCP Throughput Tests"


The document only gives guidance on how to measure RTT, bandwidth and some =
auiliary=20
parameters as RTT jitter (it does not specify how to measure these or refer=
 to=20
specifications of related measurements). I don't recall having seen referen=
ces to=20
prior related work of IPPM (last read version was draft -05).=20

All in all, I doubt that two implementors are able to measure compatible me=
trics=20
based on the documents definitions as they are by now. Even if it is only=20
"Informational" I'd prefer classification as a "framework". Many or most ot=
her=20
informational documents produced by IPPM contain Type P specifications as s=
oon as=20
metrics are to be established.

Regards,

Ruediger


-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of Hen=
k Uijterwaal
Sent: Tuesday, August 31, 2010 10:23 AM
To: IETF IPPM WG
Subject: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

IPPM Group,

This is a Working Group Last Call for the draft:

    TCP Throughput Testing Methodology
    draft-ietf-ippm-tcp-throughput-tm-06.txt

This version of the draft addresses all issues brought up on the list and
at the Maastricht meeting.  It also fixes a number of ID-nits.  The authors
believe that no further work on the draft is needed.  Note that there are
a few spelling mistakes in the draft, these will be fixed when including
any other LC comments.

Please review the draft and raise any issues by Monday, September 20,
9:00 UTC.  An URL for the draft is:

    http://www.ietf.org/id/draft-ietf-ippm-tcp-throughput-tm-06.txt

Matt & Henk


--=20
---------------------------------------------------------------------------=
---
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.ne=
t
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
---------------------------------------------------------------------------=
---

I confirm today what I denied yesterday.            Anonymous Politician.
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm

From henk@ripe.net  Mon Sep  6 01:15:16 2010
Return-Path: <henk@ripe.net>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 854293A689F for <ippm@core3.amsl.com>; Mon,  6 Sep 2010 01:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.633
X-Spam-Level: 
X-Spam-Status: No, score=-101.633 tagged_above=-999 required=5 tests=[AWL=-1.196, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m6Yw27kXTuKN for <ippm@core3.amsl.com>; Mon,  6 Sep 2010 01:15:15 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id B058E3A6897 for <ippm@ietf.org>; Mon,  6 Sep 2010 01:15:14 -0700 (PDT)
Received: from dodo.ipv6.ripe.net ([2001:610:240:23::c100:1704] helo=dodo.ripe.net) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OsWrP-0001TT-VG; Mon, 06 Sep 2010 10:15:34 +0200
Received: from [193.0.21.124] (helo=guest-100.ripe.net) by dodo.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OsWrP-0000VE-SW; Mon, 06 Sep 2010 10:15:27 +0200
Message-ID: <4C84A31F.5020908@ripe.net>
Date: Mon, 06 Sep 2010 10:15:27 +0200
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: IETF IPPM WG <ippm@ietf.org>,  Tempia Bonda Alberto <alberto.tempiabonda@telecomitalia.it>, zhenglianshu 50128 <verozheng@huawei.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d51b2aed84935f521064acf9004c298ba6
X-RIPE-Spam-Level: --
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d51b2aed84935f521064acf9004c298ba6
Subject: [ippm] Fwd: WG interest in Multicast performance monitoring drafts
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 08:15:16 -0000

IPPM group,

I have seen very few replies to this.  If you are interested in
the topic, please respond.

HEnk


-------- Original Message --------
Subject: WG interest in Multicast performance monitoring drafts
Date: Thu, 29 Jul 2010 13:52:58 +0200
From: Henk Uijterwaal <henk@ripe.net>
Organisation: RIPE NCC
To: Tempia Bonda Alberto <alberto.tempiabonda@telecomitalia.it>
CC: matt@internet2.edu <matt@internet2.edu>,  zhenglianshu 50128
<verozheng@huawei.com>, IETF IPPM WG <ippm@ietf.org>

IPPM Group,

Last Monday, Alberto and others presented this set of drafts:

> > at the upcoming IPPM meeting in Maastricht we will present a draft about
> > multicast performance monitoring
> > (draft-bipi-mboned-ip-multicast-pm-requirement-01).
> > Requirement draft:
> > http://tools.ietf.org/html/draft-bipi-mboned-ip-multicast-pm-requirement-01
> > Solution drafts:
> > http://tools.ietf.org/html/draft-liu-mboned-multicast-realstream-monitor-02
> > http://tools.ietf.org/html/draft-cociglio-mboned-multicast-pm-00

We would like to know if people consider this topic appropriate for
the IPPM WG, and if so, if there is interest to work on this topic.

The drafts discuss passive measurements of actual traffic streams, using
the metrics developed in IPPM.  In the current charter, this work is
out of scope, so picking it up would require a charter change.  Obviously,
we only want to do this if there is sufficient interest in the work.

Please respond to the list or the chairs in private by September 13.

Matt & Henk


-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
------------------------------------------------------------------------------

I confirm today what I denied yesterday.            Anonymous Politician.


From henk@ripe.net  Mon Sep  6 01:34:40 2010
Return-Path: <henk@ripe.net>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 402553A6896 for <ippm@core3.amsl.com>; Mon,  6 Sep 2010 01:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.622
X-Spam-Level: 
X-Spam-Status: No, score=-101.622 tagged_above=-999 required=5 tests=[AWL=-1.185, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B+q1+CP9bzFc for <ippm@core3.amsl.com>; Mon,  6 Sep 2010 01:34:38 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id E50693A63EC for <ippm@ietf.org>; Mon,  6 Sep 2010 01:34:37 -0700 (PDT)
Received: from dodo.ipv6.ripe.net ([2001:610:240:23::c100:1704] helo=dodo.ripe.net) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OsXAJ-00047K-V3 for ippm@ietf.org; Mon, 06 Sep 2010 10:35:06 +0200
Received: from [193.0.21.124] (helo=guest-100.ripe.net) by dodo.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OsXAJ-0001tK-Rw for ippm@ietf.org; Mon, 06 Sep 2010 10:34:59 +0200
Message-ID: <4C84A7B2.9010204@ripe.net>
Date: Mon, 06 Sep 2010 10:34:58 +0200
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: IETF IPPM WG <ippm@ietf.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d57f4adcd7dbff3f270550d4c24e2dcf26
X-RIPE-Spam-Level: --
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d57f4adcd7dbff3f270550d4c24e2dcf26
Subject: [ippm] Metrics registry discussion.
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 08:34:40 -0000

IPPM Group,

Please see below.  In Maastricht, we discussed this topic without reaching
a conclusion.  I did promise to take the discussion to the list though.

So, this is call for comments about the registry and it's future.  In
particular, I'd like to hear from people who are using the current registry,
who have developed a registry themselves for a particular application,
or who think that a different registry would be useful for them.

Note that comments made on the list so-far or at the Maastricht meeting
have been noted.  Please respond by October 15, so we can discuss
further steps by the Beijing meeting.

Henk

-------- Original Message --------
Subject: On agenda point #7
Date: Mon, 05 Jul 2010 11:28:49 +0200
From: Henk Uijterwaal <henk@ripe.net>
Organisation: RIPE NCC
To: IETF IPPM WG <ippm@ietf.org>

IPPM Group,

The Maastricht agenda has this entry:

7. Metrics registry (25)
   = Intro (Henk)
   = draft-morton-ippm-rfc4148-obsolete (Al)
   = draft-stephan-ippm-registry-ext (Emile)
   = Discussion

The background of this is the following: in RFC 4148, a registry for the IPPM
metrics has been introduced. This registry has seen very little use over the
years, mainly because the registry does not allow to store the parameters used
for every metric. That the registry isn't widely used, is best witnessed when
RFC 5644 was published and a typo was introduced in the registry. Any parser
would have detected this syntax error. Yet, it took more than 8 months before
somebody noticed. Also, the author of the original document agrees that the
registry needs to be improved.

The question is how to proceed here.  There are several options:

 a. Withdraw the current registry.  This is proposed in
    draft-morton-ippm-rfc4148-obsolete.

 b. Expand the current registry in order to make it more useful.
    This is proposed in draft-stephan-ippm-registry-ext.

 c. Drop the current registry, start with a new one from scratch.

The plan is to have 2 presentations of the draft (about 5 minutes each),
followed by a discussion.

Comments, both to the list and at the meeting, are welcome,

Henk


-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
------------------------------------------------------------------------------

I confirm today what I denied yesterday.            Anonymous Politician.


From verozheng@huawei.com  Mon Sep  6 02:49:13 2010
Return-Path: <verozheng@huawei.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 823263A68CF for <ippm@core3.amsl.com>; Mon,  6 Sep 2010 02:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.02
X-Spam-Level: 
X-Spam-Status: No, score=-3.02 tagged_above=-999 required=5 tests=[AWL=-2.526,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IROlAXJ81Tfq for <ippm@core3.amsl.com>; Mon,  6 Sep 2010 02:49:12 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id DF6113A68CE for <ippm@ietf.org>; Mon,  6 Sep 2010 02:49:11 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L8B008GHKMFEU@szxga01-in.huawei.com> for ippm@ietf.org; Mon, 06 Sep 2010 17:49:28 +0800 (CST)
Received: from z50128a ([10.110.98.60]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L8B00KB4KME28@szxga01-in.huawei.com> for ippm@ietf.org; Mon, 06 Sep 2010 17:49:27 +0800 (CST)
Date: Mon, 06 Sep 2010 17:49:26 +0800
From: Vero Zheng <verozheng@huawei.com>
In-reply-to: <151C164FE2E066418D8D44D0801543A50490E31E@S4DE8PSAAQA.mitte.t-com.de>
To: Ruediger.Geib@telekom.de
Message-id: <AD2FCFB22FFE46FBB3A2FAD7664D2CFE@z50128a>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8064.206
X-Mailer: Microsoft Windows Live Mail 14.0.8064.206
Content-type: multipart/alternative; boundary="Boundary_(ID_lcOea3C6F4+o+hFN0t5Xow)"
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
References: <9FCB2ACF14591E4DAF4180D4010E3618A777ECCD07@GRFMBX702BA020.griffon.local> <9FCB2ACF14591E4DAF4180D4010E3618A7786D7685@GRFMBX702BA020.griffon.local> <4C4FF248.1020109@ripe.net> <4C516B9A.1080502@ripe.net> <151C164FE2E066418D8D44D0801543A50490E31E@S4DE8PSAAQA.mitte.t-com.de>
Cc: Henk Uijterwaal <henk@ripe.net>, matt@internet2.edu, ippm@ietf.org
Subject: Re: [ippm] WG interest in Multicast performance monitoring drafts
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 09:49:13 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_lcOea3C6F4+o+hFN0t5Xow)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Hello Ruediger,

Thanks for your comment.
You are right that, in terms of the measurement methodology, we apply Y.1731 rather than inventing new wheels.
What we are trying to achieve in draft-liu-mboned-multicast-realstream-monitor-02
is to monitor the *real *IP multicast stream, rather than using probing packets which may yield biased or even irrelevant results.

The requirement for monitoring real multicast stream is described in draft-bipi-mboned-ip-multicast-pm-requirement-01.

Would you kindly read the requirement draft and let us know whether you are intrested in working on it.

BR,
Vero

--------------------------------------------------
From: <Ruediger.Geib@telekom.de>
Sent: Wednesday, August 25, 2010 2:46 PM
To: <henk@ripe.net>; <alberto.tempiabonda@telecomitalia.it>
Cc: <matt@internet2.edu>; <ippm@ietf.org>
Subject: Re: [ippm] WG interest in Multicast performance monitoring drafts

> Henk, 
> 
> I just had a look at
> 
>> > http://tools.ietf.org/html/draft-liu-mboned-multicast-realstream-monitor-02
> 
> The draft proposes to apply Y.1731 methodology to monitor multicast groups. While the loss measurement is active/passive, the delay measurement is clearly active. I'd suggest the authors to read RFC5644. I didn't compare details but would expect the following:
> - differences in packet loss measurement between draft-liu and RFC5644.
> - no serious difference in delay measurement methodology between draft-liu 
>  and RFC5644 (meaning that the draft-liu delay measurement method is 
>  identical with or a subset of RFC5644). 
> 
> Regards
> 
> Ruediger
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm

--Boundary_(ID_lcOea3C6F4+o+hFN0t5Xow)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.3698" name=GENERATOR></HEAD>
<BODY id=MailContainerBody 
style="PADDING-RIGHT: 10px; PADDING-LEFT: 10px; PADDING-TOP: 15px" leftMargin=0 
topMargin=0 CanvasTabStop="true" name="Compose message area">
<DIV>Hello Ruediger,<BR><BR>Thanks for your comment.<BR>You are right that, in 
terms of the measurement methodology, we apply Y.1731 rather than inventing new 
wheels.<BR>What we are trying&nbsp;to achieve in <A 
title="http://tools.ietf.org/html/draft-liu-mboned-multicast-realstream-monitor-02&#10;CTRL + Click to follow link" 
href="http://tools.ietf.org/html/draft-liu-mboned-multicast-realstream-monitor-02">draft-liu-mboned-multicast-realstream-monitor-02<A 
title="http://tools.ietf.org/html/draft-liu-mboned-multicast-realstream-monitor-02&#10;CTRL + Click to follow link" 
href="http://tools.ietf.org/html/draft-liu-mboned-multicast-realstream-monitor-02"></A><BR></A>is 
to monitor the *real *IP&nbsp;multicast stream, rather than using probing 
packets which may yield biased or even irrelevant results.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The requirement for&nbsp;monitoring real multicast stream&nbsp;is described 
in <A 
title="http://tools.ietf.org/html/draft-bipi-mboned-ip-multicast-pm-requirement-01&#10;CTRL + Click to follow link" 
href="http://tools.ietf.org/html/draft-bipi-mboned-ip-multicast-pm-requirement-01">draft-bipi-mboned-ip-multicast-pm-requirement-01</A>.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Would you kindly&nbsp;read the <A 
title="http://tools.ietf.org/html/draft-bipi-mboned-ip-multicast-pm-requirement-01&#10;CTRL + Click to follow link" 
href="http://tools.ietf.org/html/draft-bipi-mboned-ip-multicast-pm-requirement-01">requirement 
draft</A> and let us know whether you are intrested in working on it.</DIV>
<DIV>&nbsp;</DIV>
<DIV>BR,</DIV>
<DIV>Vero</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV>--------------------------------------------------<BR>From: 
&lt;Ruediger.Geib@telekom.de&gt;<BR>Sent: Wednesday, August 25, 2010 2:46 
PM<BR>To: &lt;henk@ripe.net&gt;; 
&lt;alberto.tempiabonda@telecomitalia.it&gt;<BR>Cc: &lt;matt@internet2.edu&gt;; 
&lt;ippm@ietf.org&gt;<BR>Subject: Re: [ippm] WG interest in Multicast 
performance monitoring drafts<BR><BR>&gt; Henk, <BR>&gt; <BR>&gt; I just had a 
look at<BR>&gt; <BR>&gt;&gt; &gt; 
http://tools.ietf.org/html/draft-liu-mboned-multicast-realstream-monitor-02<BR>&gt; 
<BR>&gt; The draft proposes to apply Y.1731 methodology to monitor multicast 
groups. While the loss measurement is active/passive, the delay measurement is 
clearly active. I'd suggest the authors to read RFC5644. I didn't compare 
details but would expect the following:<BR>&gt; - differences in packet loss 
measurement between draft-liu and RFC5644.<BR>&gt; - no serious difference in 
delay measurement methodology between draft-liu <BR>&gt;&nbsp; and RFC5644 
(meaning that the draft-liu delay measurement method is <BR>&gt;&nbsp; identical 
with or a subset of RFC5644). <BR>&gt; <BR>&gt; Regards<BR>&gt; <BR>&gt; 
Ruediger<BR>&gt; _______________________________________________<BR>&gt; ippm 
mailing list<BR>&gt; ippm@ietf.org<BR>&gt; 
https://www.ietf.org/mailman/listinfo/ippm</DIV></BODY></HTML>

--Boundary_(ID_lcOea3C6F4+o+hFN0t5Xow)--

From Ruediger.Geib@telekom.de  Mon Sep  6 03:50:50 2010
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 737E63A6855 for <ippm@core3.amsl.com>; Mon,  6 Sep 2010 03:50:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.655
X-Spam-Level: 
X-Spam-Status: No, score=-2.655 tagged_above=-999 required=5 tests=[AWL=0.594,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zof3ZjuEBGsG for <ippm@core3.amsl.com>; Mon,  6 Sep 2010 03:50:48 -0700 (PDT)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id C18473A67AB for <ippm@ietf.org>; Mon,  6 Sep 2010 03:50:46 -0700 (PDT)
Received: from s4de8psaans.blf.telekom.de (HELO s4de8psaans.mitte.t-com.de) ([10.151.180.168]) by tcmail71.telekom.de with ESMTP; 06 Sep 2010 12:51:11 +0200
Received: from S4DE8PSAAQA.mitte.t-com.de ([10.151.229.12]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 6 Sep 2010 12:51:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 6 Sep 2010 12:51:11 +0200
Message-ID: <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de>
In-Reply-To: <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
Thread-Index: ActI5hDf36OqIEzkTBesOmMMqCSfmwABnUUgAJsBURAAlg2kIA==
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net>
From: <Ruediger.Geib@telekom.de>
To: <Barry.Constantine@jdsu.com>
X-OriginalArrivalTime: 06 Sep 2010 10:51:10.0761 (UTC) FILETIME=[6ADD0190:01CB4DB1]
Cc: ippm@ietf.org
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 10:50:50 -0000

Hello Barry,

that's great.=20

Are you still interested in more detailed comments (like on Type-P =
proposals - I'm admittedly not an expert in specifying them), or do you =
want to finish the document largely as is? If my time allows, I can send =
some more detailed comments. But I don't want to annoy you (and would =
myself be happy if you tell me, I can save the effort).

Regards, Ruediger




Deutsche Telekom Netzproduktion GmbH
Zentrum Technik Einf=FChrung
R=FCdiger Geib
Heinrich-Hertz-Stra=DFe 3-7, 64295 Darmstadt
+49 6151 628-2747 (Tel.)
+49 251 7985 209 (Fax)
http://www.telekom.com

Erleben, was verbindet.

Deutsche Telekom Netzproduktion GmbH
Aufsichtsrat: Dr. Steffen Roehn (Vorsitzender)
Gesch=E4ftsf=FChrung: Dr. Bruno Jacobfeuerborn (Vorsitzender), Albert =
Matheis, Klaus Peren
Handelsregister: Amtsgericht Bonn HRB 14190
Sitz der Gesellschaft: Bonn
USt-IdNr. DE 814645262
-----Original Message-----
From: Barry Constantine [mailto:Barry.Constantine@jdsu.com]=20
Sent: Friday, September 03, 2010 8:08 PM
To: Geib, R=FCdiger; henk@ripe.net
Cc: ippm@ietf.org
Subject: RE: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Hello Rudi,

I think your suggestion is reasonable.

Never hurts to be explicit, so we will add Framework to the title as you =
mentioned.

We'll title it:  "Framework for TCP Throughput Testing" and add some =
reference to framework in the intro.

Thanks again,

Barry

=20

Principal Member of Technical Staff

=20

JDSU Communication Test (formerly Acterna)

Emerging Markets and Technology Research        =20

One Milestone Center Court                             =20

Germantown, MD 20876                                        =20

(W) 240-404-2227                                               =20

(C) 301-325-7069

-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of =
Ruediger.Geib@telekom.de
Sent: Tuesday, August 31, 2010 5:51 AM
To: henk@ripe.net
Cc: ippm@ietf.org
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Henk,

If time allows, I'll send more comments.

If not, here's my view:

Change the document title to

"Framework for a TCP Throughput Testing Methodology"


Arguments:

The document as is does not contain any Type P Specification. See =
definitions in

"2.2 Metrics for TCP Throughput Tests"


The document only gives guidance on how to measure RTT, bandwidth and =
some auiliary=20
parameters as RTT jitter (it does not specify how to measure these or =
refer to=20
specifications of related measurements). I don't recall having seen =
references to=20
prior related work of IPPM (last read version was draft -05).=20

All in all, I doubt that two implementors are able to measure compatible =
metrics=20
based on the documents definitions as they are by now. Even if it is =
only=20
"Informational" I'd prefer classification as a "framework". Many or most =
other=20
informational documents produced by IPPM contain Type P specifications =
as soon as=20
metrics are to be established.

Regards,

Ruediger


-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of =
Henk Uijterwaal
Sent: Tuesday, August 31, 2010 10:23 AM
To: IETF IPPM WG
Subject: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

IPPM Group,

This is a Working Group Last Call for the draft:

    TCP Throughput Testing Methodology
    draft-ietf-ippm-tcp-throughput-tm-06.txt

This version of the draft addresses all issues brought up on the list =
and
at the Maastricht meeting.  It also fixes a number of ID-nits.  The =
authors
believe that no further work on the draft is needed.  Note that there =
are
a few spelling mistakes in the draft, these will be fixed when including
any other LC comments.

Please review the draft and raise any issues by Monday, September 20,
9:00 UTC.  An URL for the draft is:

    http://www.ietf.org/id/draft-ietf-ippm-tcp-throughput-tm-06.txt

Matt & Henk


--=20
-------------------------------------------------------------------------=
-----
Henk Uijterwaal                           Email: =
henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
-------------------------------------------------------------------------=
-----

I confirm today what I denied yesterday.            Anonymous =
Politician.
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm

From henk@ripe.net  Tue Sep  7 23:52:12 2010
Return-Path: <henk@ripe.net>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B0263A67D4 for <ippm@core3.amsl.com>; Tue,  7 Sep 2010 23:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.603
X-Spam-Level: 
X-Spam-Status: No, score=-101.603 tagged_above=-999 required=5 tests=[AWL=-1.166, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUCSr1-P7vCA for <ippm@core3.amsl.com>; Tue,  7 Sep 2010 23:52:11 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id F074D3A6768 for <ippm@ietf.org>; Tue,  7 Sep 2010 23:52:10 -0700 (PDT)
Received: from ayeaye.ipv6.ripe.net ([2001:610:240:23::c100:1705] helo=ayeaye.ripe.net) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OtEWG-0005FJ-Ij for ippm@ietf.org; Wed, 08 Sep 2010 08:52:38 +0200
Received: from [193.0.21.124] (helo=guest-94.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OtEWG-0006Z2-Ez for ippm@ietf.org; Wed, 08 Sep 2010 08:52:32 +0200
Message-ID: <4C87272F.7020301@ripe.net>
Date: Wed, 08 Sep 2010 08:03:27 +0200
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: IETF IPPM WG <ippm@ietf.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d511e458145d4e09154db3e15722612aa1
X-RIPE-Spam-Level: --
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d511e458145d4e09154db3e15722612aa1
Subject: [ippm] Fwd: Important Dates for IETF 79
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2010 06:52:12 -0000

IPPM Group,

We will meet in Beijing.  Some important dates for the Beijing IETF:

2010-09-27 (Monday): Cutoff date for requests to schedule Working
Group meetings at 17:00 PT (24:00 UTC). To request a Working Group
session, use the IETF Meeting Session Request Tool.

2010-10-06 (Wednesday): Preliminary agenda published for comment.

2010-10-18 (Monday): Internet Draft Cut-off for initial document (-00)
submission by 17:00 PT (24:00 UTC), upload using IETF ID Submission
Tool.

2010-10-25 (Monday): Internet Draft final submission cut-off by 17:00
PT (24:00 UTC), upload using IETF ID Submission Tool.

Requests for agenda slots are welcome,

Henk


From Barry.Constantine@jdsu.com  Wed Sep  8 17:13:08 2010
Return-Path: <Barry.Constantine@jdsu.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 87D733A6975 for <ippm@core3.amsl.com>; Wed,  8 Sep 2010 17:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.747
X-Spam-Level: 
X-Spam-Status: No, score=-4.747 tagged_above=-999 required=5 tests=[AWL=-0.748, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6i79hDNyb364 for <ippm@core3.amsl.com>; Wed,  8 Sep 2010 17:13:05 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by core3.amsl.com (Postfix) with SMTP id 0CF613A684F for <ippm@ietf.org>; Wed,  8 Sep 2010 17:13:03 -0700 (PDT)
Received: from source ([209.36.247.244]) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKTIgmqTmJLrnVTOvBE4IZjoMqbgcSnElo@postini.com; Wed, 08 Sep 2010 17:13:32 PDT
Received: from milexhtca1.ds.jdsu.net ([10.75.2.121]) by Outbound1.jdsu.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 8 Sep 2010 17:12:57 -0700
Received: from MILEXCH1.ds.jdsu.net ([fe80::6444:f010:6d40:bdb]) by milexhtca1.ds.jdsu.net ([::1]) with mapi; Wed, 8 Sep 2010 17:12:56 -0700
From: Barry Constantine <Barry.Constantine@jdsu.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
Date: Wed, 8 Sep 2010 17:12:54 -0700
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
Thread-Index: ActI5hDf36OqIEzkTBesOmMMqCSfmwABnUUgAJsBURAAlg2kIACAkdzQ
Message-ID: <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net>
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de>
In-Reply-To: <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 09 Sep 2010 00:12:57.0190 (UTC) FILETIME=[C15B0860:01CB4FB3]
Cc: "ippm@ietf.org" <ippm@ietf.org>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 00:13:08 -0000

Hello Rudi,

Sorry for the delayed response.

We appreciate all the comments from the working group along the way to draf=
t-06; the test method has improved tremendously due to all of this interact=
ion.

We would prefer to wrap this up at this point and appreciate your directnes=
s in your question.

Thanks,

Barry

=20

Principal Member of Technical Staff

=20

JDSU Communication Test (formerly Acterna)

Emerging Markets and Technology Research        =20

One Milestone Center Court                             =20

Germantown, MD 20876                                        =20

(W) 240-404-2227                                               =20

(C) 301-325-7069

-----Original Message-----
From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]=20
Sent: Monday, September 06, 2010 6:51 AM
To: Barry Constantine
Cc: ippm@ietf.org
Subject: RE: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Hello Barry,

that's great.=20

Are you still interested in more detailed comments (like on Type-P proposal=
s - I'm admittedly not an expert in specifying them), or do you want to fin=
ish the document largely as is? If my time allows, I can send some more det=
ailed comments. But I don't want to annoy you (and would myself be happy if=
 you tell me, I can save the effort).

Regards, Ruediger




Deutsche Telekom Netzproduktion GmbH
Zentrum Technik Einf=FChrung
R=FCdiger Geib
Heinrich-Hertz-Stra=DFe 3-7, 64295 Darmstadt
+49 6151 628-2747 (Tel.)
+49 251 7985 209 (Fax)
http://www.telekom.com

Erleben, was verbindet.

Deutsche Telekom Netzproduktion GmbH
Aufsichtsrat: Dr. Steffen Roehn (Vorsitzender)
Gesch=E4ftsf=FChrung: Dr. Bruno Jacobfeuerborn (Vorsitzender), Albert Mathe=
is, Klaus Peren
Handelsregister: Amtsgericht Bonn HRB 14190
Sitz der Gesellschaft: Bonn
USt-IdNr. DE 814645262
-----Original Message-----
From: Barry Constantine [mailto:Barry.Constantine@jdsu.com]=20
Sent: Friday, September 03, 2010 8:08 PM
To: Geib, R=FCdiger; henk@ripe.net
Cc: ippm@ietf.org
Subject: RE: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Hello Rudi,

I think your suggestion is reasonable.

Never hurts to be explicit, so we will add Framework to the title as you me=
ntioned.

We'll title it:  "Framework for TCP Throughput Testing" and add some refere=
nce to framework in the intro.

Thanks again,

Barry

=20

Principal Member of Technical Staff

=20

JDSU Communication Test (formerly Acterna)

Emerging Markets and Technology Research        =20

One Milestone Center Court                             =20

Germantown, MD 20876                                        =20

(W) 240-404-2227                                               =20

(C) 301-325-7069

-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of Rue=
diger.Geib@telekom.de
Sent: Tuesday, August 31, 2010 5:51 AM
To: henk@ripe.net
Cc: ippm@ietf.org
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Henk,

If time allows, I'll send more comments.

If not, here's my view:

Change the document title to

"Framework for a TCP Throughput Testing Methodology"


Arguments:

The document as is does not contain any Type P Specification. See definitio=
ns in

"2.2 Metrics for TCP Throughput Tests"


The document only gives guidance on how to measure RTT, bandwidth and some =
auiliary=20
parameters as RTT jitter (it does not specify how to measure these or refer=
 to=20
specifications of related measurements). I don't recall having seen referen=
ces to=20
prior related work of IPPM (last read version was draft -05).=20

All in all, I doubt that two implementors are able to measure compatible me=
trics=20
based on the documents definitions as they are by now. Even if it is only=20
"Informational" I'd prefer classification as a "framework". Many or most ot=
her=20
informational documents produced by IPPM contain Type P specifications as s=
oon as=20
metrics are to be established.

Regards,

Ruediger


-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of Hen=
k Uijterwaal
Sent: Tuesday, August 31, 2010 10:23 AM
To: IETF IPPM WG
Subject: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

IPPM Group,

This is a Working Group Last Call for the draft:

    TCP Throughput Testing Methodology
    draft-ietf-ippm-tcp-throughput-tm-06.txt

This version of the draft addresses all issues brought up on the list and
at the Maastricht meeting.  It also fixes a number of ID-nits.  The authors
believe that no further work on the draft is needed.  Note that there are
a few spelling mistakes in the draft, these will be fixed when including
any other LC comments.

Please review the draft and raise any issues by Monday, September 20,
9:00 UTC.  An URL for the draft is:

    http://www.ietf.org/id/draft-ietf-ippm-tcp-throughput-tm-06.txt

Matt & Henk


--=20
---------------------------------------------------------------------------=
---
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.ne=
t
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
---------------------------------------------------------------------------=
---

I confirm today what I denied yesterday.            Anonymous Politician.
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm

From henk@ripe.net  Thu Sep  9 06:17:15 2010
Return-Path: <henk@ripe.net>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6AD93A659A for <ippm@core3.amsl.com>; Thu,  9 Sep 2010 06:17:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.657
X-Spam-Level: 
X-Spam-Status: No, score=-102.657 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KTc8x86Tda5K for <ippm@core3.amsl.com>; Thu,  9 Sep 2010 06:17:13 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id 0BD453A68D3 for <ippm@ietf.org>; Thu,  9 Sep 2010 06:17:09 -0700 (PDT)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <henk@ripe.net>) id 1Oth0I-0002b5-Th for ippm@ietf.org; Thu, 09 Sep 2010 15:17:35 +0200
Received: from [193.0.21.124] (helo=guest-94.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1Oth0I-0005T7-JH for ippm@ietf.org; Thu, 09 Sep 2010 15:17:26 +0200
Message-ID: <4C88DE66.3010804@ripe.net>
Date: Thu, 09 Sep 2010 15:17:26 +0200
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: ippm@ietf.org
References: <4C7CBBFD.1030402@ripe.net>
In-Reply-To: <4C7CBBFD.1030402@ripe.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5f6abf7d51880aa9b0c10dd0327681744
X-RIPE-Spam-Level: --
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5f6abf7d51880aa9b0c10dd0327681744
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 13:17:16 -0000

Hi Barry and others,

> This is a Working Group Last Call for the draft:
> 
>     TCP Throughput Testing Methodology
>     draft-ietf-ippm-tcp-throughput-tm-06.txt

Details, as a participant, not WG chair.

1. Introduction: I think the first paragraph has to come after the 1st
   sentence of the 2nd one.  TCP testing is useful in itself, turn-up
   testing is an use case.

2. Section 2: "Some specific goals".  Remove some, either you list all
   goals or you explicitely state which goals are omitted.

3. Section 2.2.  With this definition, tcp efficiency can become <0%,
   which is hard to interpret.  (Suppose all bytes are resent twice,
   admittedly a strange case).  Work-around: if <0, make it 0.  (The
   connection is not useful anyway).

4. Section 3, item #2.  For Round Trip, put in a reference to the RFC
   on 2-way delay.  If this is clear, then 2 results from different
   vendors will be more comparable.

5. Section 3.2.2.  I think we should either select one or al least
   make it a MUST that this is reported.  Otherwise it will be hard to
   compare results.

6. Section 6: Drop the first paragraph. "The author" is undefined with
   4 authors.

I already sent you a couple of spelling errors.

Henk


-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
------------------------------------------------------------------------------

I confirm today what I denied yesterday.            Anonymous Politician.

From Barry.Constantine@jdsu.com  Thu Sep  9 07:12:22 2010
Return-Path: <Barry.Constantine@jdsu.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 860F73A68CB for <ippm@core3.amsl.com>; Thu,  9 Sep 2010 07:12:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.953
X-Spam-Level: 
X-Spam-Status: No, score=-5.953 tagged_above=-999 required=5 tests=[AWL=0.646,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IJUpMuWCQJJs for <ippm@core3.amsl.com>; Thu,  9 Sep 2010 07:12:18 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by core3.amsl.com (Postfix) with SMTP id B14333A6868 for <ippm@ietf.org>; Thu,  9 Sep 2010 07:12:16 -0700 (PDT)
Received: from source ([209.36.247.245]) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKTIjrW1e8DCyBdtrRcDJ0RXYPCCjjKg/g@postini.com; Thu, 09 Sep 2010 07:12:46 PDT
Received: from milexhtca2.ds.jdsu.net ([10.75.2.122]) by Outbound2.jdsu.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 9 Sep 2010 07:04:07 -0700
Received: from MILEXCH1.ds.jdsu.net ([fe80::6444:f010:6d40:bdb]) by milexhtca2.ds.jdsu.net ([::1]) with mapi; Thu, 9 Sep 2010 07:04:07 -0700
From: Barry Constantine <Barry.Constantine@jdsu.com>
To: Henk Uijterwaal <henk@ripe.net>, "ippm@ietf.org" <ippm@ietf.org>
Date: Thu, 9 Sep 2010 07:04:06 -0700
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
Thread-Index: ActQIXpiZtye5LRtRF2oYsU/yTg/cQABlVDQ
Message-ID: <94DEE80C63F7D34F9DC9FE69E39436BE38BA05A652@MILEXCH1.ds.jdsu.net>
References: <4C7CBBFD.1030402@ripe.net> <4C88DE66.3010804@ripe.net>
In-Reply-To: <4C88DE66.3010804@ripe.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 09 Sep 2010 14:04:07.0979 (UTC) FILETIME=[DEA987B0:01CB5027]
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 14:12:22 -0000

Very good comments, Henk I will them all to the next draft.

Thanks again,

Barry

=20

Principal Member of Technical Staff

=20

JDSU Communication Test (formerly Acterna)

Emerging Markets and Technology Research        =20

One Milestone Center Court                             =20

Germantown, MD 20876                                        =20

(W) 240-404-2227                                               =20

(C) 301-325-7069

-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of Hen=
k Uijterwaal
Sent: Thursday, September 09, 2010 9:17 AM
To: ippm@ietf.org
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Hi Barry and others,

> This is a Working Group Last Call for the draft:
>=20
>     TCP Throughput Testing Methodology
>     draft-ietf-ippm-tcp-throughput-tm-06.txt

Details, as a participant, not WG chair.

1. Introduction: I think the first paragraph has to come after the 1st
   sentence of the 2nd one.  TCP testing is useful in itself, turn-up
   testing is an use case.

2. Section 2: "Some specific goals".  Remove some, either you list all
   goals or you explicitely state which goals are omitted.

3. Section 2.2.  With this definition, tcp efficiency can become <0%,
   which is hard to interpret.  (Suppose all bytes are resent twice,
   admittedly a strange case).  Work-around: if <0, make it 0.  (The
   connection is not useful anyway).

4. Section 3, item #2.  For Round Trip, put in a reference to the RFC
   on 2-way delay.  If this is clear, then 2 results from different
   vendors will be more comparable.

5. Section 3.2.2.  I think we should either select one or al least
   make it a MUST that this is reported.  Otherwise it will be hard to
   compare results.

6. Section 6: Drop the first paragraph. "The author" is undefined with
   4 authors.

I already sent you a couple of spelling errors.

Henk


--=20
---------------------------------------------------------------------------=
---
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.ne=
t
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
---------------------------------------------------------------------------=
---

I confirm today what I denied yesterday.            Anonymous Politician.
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm

From Ruediger.Geib@telekom.de  Fri Sep 10 06:26:28 2010
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64A043A6A4B for <ippm@core3.amsl.com>; Fri, 10 Sep 2010 06:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.583
X-Spam-Level: 
X-Spam-Status: No, score=0.583 tagged_above=-999 required=5 tests=[AWL=-3.027,  BAYES_20=-0.74, GB_SUMOF=5, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YcwvBmu6YUj3 for <ippm@core3.amsl.com>; Fri, 10 Sep 2010 06:26:27 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by core3.amsl.com (Postfix) with ESMTP id 3D2403A6A4A for <ippm@ietf.org>; Fri, 10 Sep 2010 06:26:27 -0700 (PDT)
Received: from s4de8psaans.blf.telekom.de (HELO s4de8psaans.mitte.t-com.de) ([10.151.180.168]) by tcmail31.telekom.de with ESMTP; 10 Sep 2010 15:26:28 +0200
Received: from S4DE8PSAAQA.mitte.t-com.de ([10.151.229.12]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 10 Sep 2010 15:26:28 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 10 Sep 2010 15:26:26 +0200
Message-ID: <151C164FE2E066418D8D44D0801543A504B0DFD9@S4DE8PSAAQA.mitte.t-com.de>
In-Reply-To: <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
Thread-Index: ActI5hDf36OqIEzkTBesOmMMqCSfmwABnUUgAJsBURAAlg2kIACAkdzQAEvRcvA=
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net>
From: <Ruediger.Geib@telekom.de>
To: <Barry.Constantine@jdsu.com>
X-OriginalArrivalTime: 10 Sep 2010 13:26:28.0075 (UTC) FILETIME=[C6114BB0:01CB50EB]
Cc: ippm@ietf.org
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2010 13:26:28 -0000

Hi Barry,

Part 1 of the comments. Edirorial text changes express my taste. I don't =
insist on them. Comments Part 2 follows, if time allows.

Regards, Ruediger

-----

1. Introduction - Editorial

Last section may be reworded to

   This framework proposes a test which should be performed in addisiont =

   to traditional Layer 2/3 type tests, which are conducted to verify =
the=20
   integrity of the network before conducting TCP tests. Examples =
include=20
   RFC 2544 [RFC2544], iperf (UDP mode), or manual packet layer test=20
   techniques where packet throughput, loss, and delay measurements=20
   are conducted.
----

2. Goals of this Methodology

...are not intended to be measured or analyzed by such a methodology.

Please add
   - a method to operate permanently with high measurement loads. TCP=20
     performance and optimisation data of operational networks may be=20
     captured and evaluated by using data of the "TCP Extended=20
     Statistics MIB" [RFC4898].=20

<-- Please add a reference to RFC 4898 or explain why it can't be used =
-->

----

2.2 Metrics for TCP Throughput

Henk had a comment here which may have been caused by the lack of a=20
definition of "transmitted bytes". Please add a definition of the terms=20
"Transmitted bytes" and "retransmitted Bytes". If the former is the sum =
of=20
"Succesfully transmitted bytes" and "retransmitted bytes", that would =
solve=20
Henk's problem, as then Transmitted Bytes > Retransmitted Bytes.=20

Effectively your formula then is: received bytes/transmitted bytes.

You introduce some type P like singletons in the following:

- type-P-TCP Transmitted Bytes
- type-P-TCP Retransmitted Bytes
- type-P-TCP Efficiency (you've defined a formula)

These depend on a number of parameters which may vary:
RTT, Packet Loss, MSS, Path Capacity, MTU size and the time when=20
you've measured.

You then introduce another two type P like singletons,=20

- type-P-TCP Actual Transfer Time
- type-P-TCP Transfer Index

In adition to the above parameters, both depend on a data block size=20
and the transfer index in addition depends on an "ideal TCP transfer=20
time".

There's no definition of the "ideal TCP transfer time" - at least I =
didn't=20
see any before or immediately after the Transfer Index is introduced. =20
This should be added.

I've tried to scetch some Type-P language here and based it on your=20
input. I leave it to you to pick it up. I'm not an expert on type p=20
definitions, this definitely requires more work.

----------Finish for today--------


From Barry.Constantine@jdsu.com  Fri Sep 10 06:46:01 2010
Return-Path: <Barry.Constantine@jdsu.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFD323A67A7 for <ippm@core3.amsl.com>; Fri, 10 Sep 2010 06:46:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.525
X-Spam-Level: 
X-Spam-Status: No, score=-3.525 tagged_above=-999 required=5 tests=[AWL=-1.926, BAYES_00=-2.599, GB_SUMOF=5, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zT5c4PFYKuzc for <ippm@core3.amsl.com>; Fri, 10 Sep 2010 06:46:00 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by core3.amsl.com (Postfix) with SMTP id A804D3A6403 for <ippm@ietf.org>; Fri, 10 Sep 2010 06:46:00 -0700 (PDT)
Received: from source ([209.36.247.244]) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKTIo2sgg8d5iBtRqJ2qZg86jFl2t1C5Ae@postini.com; Fri, 10 Sep 2010 06:46:28 PDT
Received: from milexhtca2.ds.jdsu.net ([10.75.2.122]) by Outbound1.jdsu.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 10 Sep 2010 06:44:22 -0700
Received: from MILEXCH1.ds.jdsu.net ([fe80::6444:f010:6d40:bdb]) by milexhtca2.ds.jdsu.net ([::1]) with mapi; Fri, 10 Sep 2010 06:44:22 -0700
From: Barry Constantine <Barry.Constantine@jdsu.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
Date: Fri, 10 Sep 2010 06:44:21 -0700
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
Thread-Index: ActI5hDf36OqIEzkTBesOmMMqCSfmwABnUUgAJsBURAAlg2kIACAkdzQAEvRcvAAAtibYA==
Message-ID: <94DEE80C63F7D34F9DC9FE69E39436BE38BA05AE77@MILEXCH1.ds.jdsu.net>
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504B0DFD9@S4DE8PSAAQA.mitte.t-com.de>
In-Reply-To: <151C164FE2E066418D8D44D0801543A504B0DFD9@S4DE8PSAAQA.mitte.t-com.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 10 Sep 2010 13:44:22.0894 (UTC) FILETIME=[46B5A8E0:01CB50EE]
Cc: "ippm@ietf.org" <ippm@ietf.org>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2010 13:46:02 -0000

Rudi,

Thank you for your additional comments.

I thought we agreed that if this were to be retitled a framework (and infor=
mational versus a standard), then the Type P metrics could remain unaddress=
ed.

Please let me know if I am misunderstanding, will definitely incorporate yo=
ur comments in this email (minus the Type P metric work).


Thanks,

Barry

=20

Principal Member of Technical Staff

=20

JDSU Communication Test (formerly Acterna)

Emerging Markets and Technology Research        =20

One Milestone Center Court                             =20

Germantown, MD 20876                                        =20

(W) 240-404-2227                                               =20

(C) 301-325-7069


-----Original Message-----
From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]=20
Sent: Friday, September 10, 2010 9:26 AM
To: Barry Constantine
Cc: ippm@ietf.org
Subject: RE: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Hi Barry,

Part 1 of the comments. Edirorial text changes express my taste. I don't in=
sist on them. Comments Part 2 follows, if time allows.

Regards, Ruediger

-----

1. Introduction - Editorial

Last section may be reworded to

   This framework proposes a test which should be performed in addisiont=20
   to traditional Layer 2/3 type tests, which are conducted to verify the=20
   integrity of the network before conducting TCP tests. Examples include=20
   RFC 2544 [RFC2544], iperf (UDP mode), or manual packet layer test=20
   techniques where packet throughput, loss, and delay measurements=20
   are conducted.
----

2. Goals of this Methodology

...are not intended to be measured or analyzed by such a methodology.

Please add
   - a method to operate permanently with high measurement loads. TCP=20
     performance and optimisation data of operational networks may be=20
     captured and evaluated by using data of the "TCP Extended=20
     Statistics MIB" [RFC4898].=20

<-- Please add a reference to RFC 4898 or explain why it can't be used -->

----

2.2 Metrics for TCP Throughput

Henk had a comment here which may have been caused by the lack of a=20
definition of "transmitted bytes". Please add a definition of the terms=20
"Transmitted bytes" and "retransmitted Bytes". If the former is the sum of=
=20
"Succesfully transmitted bytes" and "retransmitted bytes", that would solve=
=20
Henk's problem, as then Transmitted Bytes > Retransmitted Bytes.=20

Effectively your formula then is: received bytes/transmitted bytes.

You introduce some type P like singletons in the following:

- type-P-TCP Transmitted Bytes
- type-P-TCP Retransmitted Bytes
- type-P-TCP Efficiency (you've defined a formula)

These depend on a number of parameters which may vary:
RTT, Packet Loss, MSS, Path Capacity, MTU size and the time when=20
you've measured.

You then introduce another two type P like singletons,=20

- type-P-TCP Actual Transfer Time
- type-P-TCP Transfer Index

In adition to the above parameters, both depend on a data block size=20
and the transfer index in addition depends on an "ideal TCP transfer=20
time".

There's no definition of the "ideal TCP transfer time" - at least I didn't=
=20
see any before or immediately after the Transfer Index is introduced. =20
This should be added.

I've tried to scetch some Type-P language here and based it on your=20
input. I leave it to you to pick it up. I'm not an expert on type p=20
definitions, this definitely requires more work.

----------Finish for today--------


From acmorton@att.com  Fri Sep 10 07:14:46 2010
Return-Path: <acmorton@att.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 634883A6A45 for <ippm@core3.amsl.com>; Fri, 10 Sep 2010 07:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.115
X-Spam-Level: 
X-Spam-Status: No, score=-103.115 tagged_above=-999 required=5 tests=[AWL=-2.319, BAYES_00=-2.599, GB_SUMOF=5, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2VMgiLm8ZYhX for <ippm@core3.amsl.com>; Fri, 10 Sep 2010 07:14:45 -0700 (PDT)
Received: from mail129.messagelabs.com (mail129.messagelabs.com [216.82.250.147]) by core3.amsl.com (Postfix) with ESMTP id CCB603A6A61 for <ippm@ietf.org>; Fri, 10 Sep 2010 07:13:20 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-12.tower-129.messagelabs.com!1284128027!17563397!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 7071 invoked from network); 10 Sep 2010 14:13:47 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-12.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Sep 2010 14:13:47 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o8AEE3qa011774 for <ippm@ietf.org>; Fri, 10 Sep 2010 10:14:03 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o8AEDw7Y011668 for <ippm@ietf.org>; Fri, 10 Sep 2010 10:13:59 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id o8AEDgUH017811 for <ippm@ietf.org>; Fri, 10 Sep 2010 10:13:42 -0400
Received: from mailgw1.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id o8AEDavF017611 for <ippm@ietf.org>; Fri, 10 Sep 2010 10:13:36 -0400
Message-Id: <201009101413.o8AEDavF017611@alpd052.aldc.att.com>
Received: from acmt.att.com (ds135-16-251-236.dhcps.ugn.att.com[135.16.251.236](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20100910141331gw100627t8e>; Fri, 10 Sep 2010 14:13:36 +0000
X-Originating-IP: [135.16.251.236]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 10 Sep 2010 10:13:53 -0400
To: Barry Constantine <Barry.Constantine@jdsu.com>, "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
From: Al Morton <acmorton@att.com>
In-Reply-To: <94DEE80C63F7D34F9DC9FE69E39436BE38BA05AE77@MILEXCH1.ds.jds u.net>
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504B0DFD9@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38BA05AE77@MILEXCH1.ds.jdsu.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "ippm@ietf.org" <ippm@ietf.org>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2010 14:14:46 -0000

Barry, Rudi,

My recollection from the March IPPM session is that
  - we agreed to take this up as an Informational RFC
  - we aren't defining metrics here
   (if we were, it would be standards track)

So, I agree with the "Framework" title change.
I would clarify that "Type-P" metric specifications
are un-attempted with this scope (what the draft does now).

I will hopefully add some more comments later today (sigh).

regards,
Al

At 09:44 AM 9/10/2010, Barry Constantine wrote:
>...
>I thought we agreed that if this were to be retitled a framework 
>(and informational versus a standard), then the Type P metrics could 
>remain unaddressed.
>
>Please let me know if I am misunderstanding, will definitely 
>incorporate your comments in this email (minus the Type P metric work).
>
>
>Thanks,
>
>Barry
>
>
>
>Principal Member of Technical Staff
>
>
>
>JDSU Communication Test (formerly Acterna)
>
>Emerging Markets and Technology Research
>
>One Milestone Center Court
>
>Germantown, MD 20876
>
>(W) 240-404-2227
>
>(C) 301-325-7069
>
>
>-----Original Message-----
>From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]
>Sent: Friday, September 10, 2010 9:26 AM
>To: Barry Constantine
>Cc: ippm@ietf.org
>Subject: RE: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
>
>Hi Barry,
>
>Part 1 of the comments. Edirorial text changes express my taste. I 
>don't insist on them. Comments Part 2 follows, if time allows.
>
>Regards, Ruediger
>
>-----
>
>1. Introduction - Editorial
>
>Last section may be reworded to
>
>    This framework proposes a test which should be performed in addisiont
>    to traditional Layer 2/3 type tests, which are conducted to verify the
>    integrity of the network before conducting TCP tests. Examples include
>    RFC 2544 [RFC2544], iperf (UDP mode), or manual packet layer test
>    techniques where packet throughput, loss, and delay measurements
>    are conducted.
>----
>
>2. Goals of this Methodology
>
>...are not intended to be measured or analyzed by such a methodology.
>
>Please add
>    - a method to operate permanently with high measurement loads. TCP
>      performance and optimisation data of operational networks may be
>      captured and evaluated by using data of the "TCP Extended
>      Statistics MIB" [RFC4898].
>
><-- Please add a reference to RFC 4898 or explain why it can't be used -->
>
>----
>
>2.2 Metrics for TCP Throughput
>
>Henk had a comment here which may have been caused by the lack of a
>definition of "transmitted bytes". Please add a definition of the terms
>"Transmitted bytes" and "retransmitted Bytes". If the former is the sum of
>"Succesfully transmitted bytes" and "retransmitted bytes", that would solve
>Henk's problem, as then Transmitted Bytes > Retransmitted Bytes.
>
>Effectively your formula then is: received bytes/transmitted bytes.
>
>You introduce some type P like singletons in the following:
>
>- type-P-TCP Transmitted Bytes
>- type-P-TCP Retransmitted Bytes
>- type-P-TCP Efficiency (you've defined a formula)
>
>These depend on a number of parameters which may vary:
>RTT, Packet Loss, MSS, Path Capacity, MTU size and the time when
>you've measured.
>
>You then introduce another two type P like singletons,
>
>- type-P-TCP Actual Transfer Time
>- type-P-TCP Transfer Index
>
>In adition to the above parameters, both depend on a data block size
>and the transfer index in addition depends on an "ideal TCP transfer
>time".
>
>There's no definition of the "ideal TCP transfer time" - at least I didn't
>see any before or immediately after the Transfer Index is introduced.
>This should be added.
>
>I've tried to scetch some Type-P language here and based it on your
>input. I leave it to you to pick it up. I'm not an expert on type p
>definitions, this definitely requires more work.
>
>----------Finish for today--------
>
>_______________________________________________
>ippm mailing list
>ippm@ietf.org
>https://www.ietf.org/mailman/listinfo/ippm


From Ruediger.Geib@telekom.de  Mon Sep 13 01:51:36 2010
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F379D3A6842 for <ippm@core3.amsl.com>; Mon, 13 Sep 2010 01:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.091
X-Spam-Level: *
X-Spam-Status: No, score=1.091 tagged_above=-999 required=5 tests=[AWL=-3.260,  BAYES_50=0.001, GB_SUMOF=5, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 487tlhCFvmPw for <ippm@core3.amsl.com>; Mon, 13 Sep 2010 01:51:35 -0700 (PDT)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id AD7D53A6822 for <ippm@ietf.org>; Mon, 13 Sep 2010 01:51:33 -0700 (PDT)
Received: from s4de8psaanq.blf.telekom.de (HELO S4DE8PSAANQ.mitte.t-com.de) ([10.151.180.166]) by tcmail71.telekom.de with ESMTP; 13 Sep 2010 10:51:09 +0200
Received: from S4DE8PSAAQA.mitte.t-com.de ([10.151.229.12]) by S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Sep 2010 10:51:08 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 13 Sep 2010 10:51:04 +0200
Message-ID: <151C164FE2E066418D8D44D0801543A504B0E4EB@S4DE8PSAAQA.mitte.t-com.de>
In-Reply-To: <94DEE80C63F7D34F9DC9FE69E39436BE38BA05AE77@MILEXCH1.ds.jdsu.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
Thread-Index: ActI5hDf36OqIEzkTBesOmMMqCSfmwABnUUgAJsBURAAlg2kIACAkdzQAEvRcvAAAtibYACMtMYg
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504B0DFD9@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38BA05AE77@MILEXCH1.ds.jdsu.net>
From: <Ruediger.Geib@telekom.de>
To: <Barry.Constantine@jdsu.com>
X-OriginalArrivalTime: 13 Sep 2010 08:51:08.0024 (UTC) FILETIME=[CE96CF80:01CB5320]
Cc: ippm@ietf.org
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Sep 2010 08:51:36 -0000

Hi Barry,

I don't insist on the Type-P stuff, the comment was meant as an offer, =
should you want to go there.

Part 2 of my comments will follow this mail.

Regards,

Ruediger

-----Original Message-----
From: Barry Constantine [mailto:Barry.Constantine@jdsu.com]=20
Sent: Friday, September 10, 2010 3:44 PM
To: Geib, R=FCdiger
Cc: ippm@ietf.org
Subject: RE: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Rudi,

Thank you for your additional comments.

I thought we agreed that if this were to be retitled a framework (and =
informational versus a standard), then the Type P metrics could remain =
unaddressed.

Please let me know if I am misunderstanding, will definitely incorporate =
your comments in this email (minus the Type P metric work).


Thanks,

Barry

=20

Principal Member of Technical Staff

=20

JDSU Communication Test (formerly Acterna)

Emerging Markets and Technology Research        =20

One Milestone Center Court                             =20

Germantown, MD 20876                                        =20

(W) 240-404-2227                                               =20

(C) 301-325-7069


-----Original Message-----
From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]=20
Sent: Friday, September 10, 2010 9:26 AM
To: Barry Constantine
Cc: ippm@ietf.org
Subject: RE: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Hi Barry,

Part 1 of the comments. Edirorial text changes express my taste. I don't =
insist on them. Comments Part 2 follows, if time allows.

Regards, Ruediger

-----

1. Introduction - Editorial

Last section may be reworded to

   This framework proposes a test which should be performed in addisiont =

   to traditional Layer 2/3 type tests, which are conducted to verify =
the=20
   integrity of the network before conducting TCP tests. Examples =
include=20
   RFC 2544 [RFC2544], iperf (UDP mode), or manual packet layer test=20
   techniques where packet throughput, loss, and delay measurements=20
   are conducted.
----

2. Goals of this Methodology

...are not intended to be measured or analyzed by such a methodology.

Please add
   - a method to operate permanently with high measurement loads. TCP=20
     performance and optimisation data of operational networks may be=20
     captured and evaluated by using data of the "TCP Extended=20
     Statistics MIB" [RFC4898].=20

<-- Please add a reference to RFC 4898 or explain why it can't be used =
-->

----

2.2 Metrics for TCP Throughput

Henk had a comment here which may have been caused by the lack of a=20
definition of "transmitted bytes". Please add a definition of the terms=20
"Transmitted bytes" and "retransmitted Bytes". If the former is the sum =
of=20
"Succesfully transmitted bytes" and "retransmitted bytes", that would =
solve=20
Henk's problem, as then Transmitted Bytes > Retransmitted Bytes.=20

Effectively your formula then is: received bytes/transmitted bytes.

You introduce some type P like singletons in the following:

- type-P-TCP Transmitted Bytes
- type-P-TCP Retransmitted Bytes
- type-P-TCP Efficiency (you've defined a formula)

These depend on a number of parameters which may vary:
RTT, Packet Loss, MSS, Path Capacity, MTU size and the time when=20
you've measured.

You then introduce another two type P like singletons,=20

- type-P-TCP Actual Transfer Time
- type-P-TCP Transfer Index

In adition to the above parameters, both depend on a data block size=20
and the transfer index in addition depends on an "ideal TCP transfer=20
time".

There's no definition of the "ideal TCP transfer time" - at least I =
didn't=20
see any before or immediately after the Transfer Index is introduced. =20
This should be added.

I've tried to scetch some Type-P language here and based it on your=20
input. I leave it to you to pick it up. I'm not an expert on type p=20
definitions, this definitely requires more work.

----------Finish for today--------


From Ruediger.Geib@telekom.de  Mon Sep 13 01:54:49 2010
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9C253A690D for <ippm@core3.amsl.com>; Mon, 13 Sep 2010 01:54:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.137
X-Spam-Level: 
X-Spam-Status: No, score=-1.137 tagged_above=-999 required=5 tests=[AWL=-0.488, BAYES_50=0.001, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Splrqk5oVVZf for <ippm@core3.amsl.com>; Mon, 13 Sep 2010 01:54:48 -0700 (PDT)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id 67CD23A691B for <ippm@ietf.org>; Mon, 13 Sep 2010 01:54:48 -0700 (PDT)
Received: from s4de8psaanq.blf.telekom.de (HELO S4DE8PSAANQ.mitte.t-com.de) ([10.151.180.166]) by tcmail71.telekom.de with ESMTP; 13 Sep 2010 10:55:13 +0200
Received: from S4DE8PSAAQA.mitte.t-com.de ([10.151.229.12]) by S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Sep 2010 10:55:13 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 13 Sep 2010 10:55:12 +0200
Message-ID: <151C164FE2E066418D8D44D0801543A504B0E50D@S4DE8PSAAQA.mitte.t-com.de>
In-Reply-To: <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt - part 2
Thread-Index: ActI5hDf36OqIEzkTBesOmMMqCSfmwABnUUgAJsBURAAlg2kIACAkdzQAEvRcvA=
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net>
From: <Ruediger.Geib@telekom.de>
To: <Barry.Constantine@jdsu.com>
X-OriginalArrivalTime: 13 Sep 2010 08:55:13.0790 (UTC) FILETIME=[6113B9E0:01CB5321]
Cc: ippm@ietf.org
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt - part 2
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Sep 2010 08:54:49 -0000

Hi Barry,

Part 2 of the comments. Edirorial text changes express my taste. I don't =
insist on them. Comments Part 3 follows, if time allows.

Regards, Ruediger


-----

A general comment: the document does not offer any section on=20
terminology or test set up architecture. This causes a fair=20
share of my questions.

-----

3. TCP Throughput Testing Methodology

....
4. Traffic Management Tests.  ....
   Multiple connection testing can verify that the network is configured
   properly for traffic shaping versus policing, various queueing=20
   implementations, and RED.

<Please clarify which network element configurations are supposed to be=20
characterised that way, eg. CE routers, PE routers, P routers or all=20
network elements along a path. If PE or P routers are to be tested,=20
please add a statement whether you expect such tests to be carried=20
out by the operational staff of the provider or in cooperation with=20
these.>

----

Same section, later

   Whether the TCP test host is a standard computer or dedicated test
   instrument, the following areas should be considered when selecting
   a test host:

   - TCP implementation used by the test host OS, i.e. Linux OS kernel=20
   using TCP Reno, TCP options supported, etc.  This will obviously be=20
   more important when using custom test equipment where the TCP=20
   implementation may be customized or tuned to run in higher=20
   performance hardware

<If there is any requirement to use a standard conformant TCP=20
implementation, the text should express this using standard language.=20
Is it clear to any reader why exactly the TCP implementation=20
is an issue by just reading the above text? Or do you expect a certain=20
know how level to understand this issue?  MUST or SHOULD the=20
implementation used by the test equipment be recorded when performing=20
a test?>

----

Same section, later

   - Most importantly, the TCP test host must be capable of generating=20
   and receiving stateful TCP test traffic at the full link speed of the =

   network under test. As a general rule of thumb, testing TCP=20
   throughput at rates greater than 100 Mbit/sec generally requires high
   performance server hardware or dedicated hardware based test tools.

<Is the first "must" meant to be a "MUST"?>
<Please clarify whether the "network under test" is the Layer 2/3 VPN =
with=20
the access bandwidth agreed for this network or the complete provider=20
network accross which the Layer 2/3 VPN is produced.>

----

Same section, later

   - To measure RTT and TCP Efficiency per connection, this will=20
   generally require dedicated hardware based test tools. In the absence
   of dedicated hardware based test tools, these measurements may need=20
   to be conducted with packet capture tools (conduct TCP throughput=20
   tests and analyze RTT and retransmission results with packet=20
   captures).

<Please add a reference for the "TCP Extended Statistics MIB" [RFC4898]=20
and adapt text, as this might be a way get around dedicated test=20
equipment and packet capture tools.>=20

<Please add an additional section expressing something like:>

  - The test equipment and its acces to the network under test MUST NOT=20
introduce a performance bottleneck of any kind.

----------Finish for today--------


From Barry.Constantine@jdsu.com  Mon Sep 13 06:19:39 2010
Return-Path: <Barry.Constantine@jdsu.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC2873A69C8 for <ippm@core3.amsl.com>; Mon, 13 Sep 2010 06:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.333
X-Spam-Level: 
X-Spam-Status: No, score=-3.333 tagged_above=-999 required=5 tests=[AWL=-1.733, BAYES_00=-2.599, GB_SUMOF=5, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DcRGNKJ9kqmc for <ippm@core3.amsl.com>; Mon, 13 Sep 2010 06:19:38 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by core3.amsl.com (Postfix) with SMTP id AD7A93A6826 for <ippm@ietf.org>; Mon, 13 Sep 2010 06:19:38 -0700 (PDT)
Received: from source ([209.36.247.244]) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKTI4k/Ob7oJ5QlxezV+oMAeqM9s91uXGF@postini.com; Mon, 13 Sep 2010 06:20:05 PDT
Received: from milexhtca1.ds.jdsu.net ([10.75.2.121]) by Outbound1.jdsu.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Sep 2010 06:19:02 -0700
Received: from MILEXCH1.ds.jdsu.net ([fe80::6444:f010:6d40:bdb]) by milexhtca1.ds.jdsu.net ([::1]) with mapi; Mon, 13 Sep 2010 06:19:01 -0700
From: Barry Constantine <Barry.Constantine@jdsu.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
Date: Mon, 13 Sep 2010 06:19:00 -0700
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
Thread-Index: ActI5hDf36OqIEzkTBesOmMMqCSfmwABnUUgAJsBURAAlg2kIACAkdzQAEvRcvAAmO5owA==
Message-ID: <94DEE80C63F7D34F9DC9FE69E39436BE38BA0CD4C6@MILEXCH1.ds.jdsu.net>
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504B0DFD9@S4DE8PSAAQA.mitte.t-com.de>
In-Reply-To: <151C164FE2E066418D8D44D0801543A504B0DFD9@S4DE8PSAAQA.mitte.t-com.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 13 Sep 2010 13:19:02.0151 (UTC) FILETIME=[3B83F170:01CB5346]
Cc: "ippm@ietf.org" <ippm@ietf.org>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Sep 2010 13:19:39 -0000

Hi Rudi,

Just to properly close these comments; we agree to the Section 1. and 2. co=
mments and will incorporate this into the final draft.

Looking at your comments from today and will get back to you this week.

Thanks,

Barry

=20

Principal Member of Technical Staff

=20

JDSU Communication Test (formerly Acterna)

Emerging Markets and Technology Research        =20

One Milestone Center Court                             =20

Germantown, MD 20876                                        =20

(W) 240-404-2227                                               =20

(C) 301-325-7069


-----Original Message-----
From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]=20
Sent: Friday, September 10, 2010 9:26 AM
To: Barry Constantine
Cc: ippm@ietf.org
Subject: RE: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Hi Barry,

Part 1 of the comments. Edirorial text changes express my taste. I don't in=
sist on them. Comments Part 2 follows, if time allows.

Regards, Ruediger

-----

1. Introduction - Editorial

Last section may be reworded to

   This framework proposes a test which should be performed in addisiont=20
   to traditional Layer 2/3 type tests, which are conducted to verify the=20
   integrity of the network before conducting TCP tests. Examples include=20
   RFC 2544 [RFC2544], iperf (UDP mode), or manual packet layer test=20
   techniques where packet throughput, loss, and delay measurements=20
   are conducted.
----

2. Goals of this Methodology

...are not intended to be measured or analyzed by such a methodology.

Please add
   - a method to operate permanently with high measurement loads. TCP=20
     performance and optimisation data of operational networks may be=20
     captured and evaluated by using data of the "TCP Extended=20
     Statistics MIB" [RFC4898].=20

<-- Please add a reference to RFC 4898 or explain why it can't be used -->

----

2.2 Metrics for TCP Throughput

Henk had a comment here which may have been caused by the lack of a=20
definition of "transmitted bytes". Please add a definition of the terms=20
"Transmitted bytes" and "retransmitted Bytes". If the former is the sum of=
=20
"Succesfully transmitted bytes" and "retransmitted bytes", that would solve=
=20
Henk's problem, as then Transmitted Bytes > Retransmitted Bytes.=20

Effectively your formula then is: received bytes/transmitted bytes.

You introduce some type P like singletons in the following:

- type-P-TCP Transmitted Bytes
- type-P-TCP Retransmitted Bytes
- type-P-TCP Efficiency (you've defined a formula)

These depend on a number of parameters which may vary:
RTT, Packet Loss, MSS, Path Capacity, MTU size and the time when=20
you've measured.

You then introduce another two type P like singletons,=20

- type-P-TCP Actual Transfer Time
- type-P-TCP Transfer Index

In adition to the above parameters, both depend on a data block size=20
and the transfer index in addition depends on an "ideal TCP transfer=20
time".

There's no definition of the "ideal TCP transfer time" - at least I didn't=
=20
see any before or immediately after the Transfer Index is introduced. =20
This should be added.

I've tried to scetch some Type-P language here and based it on your=20
input. I leave it to you to pick it up. I'm not an expert on type p=20
definitions, this definitely requires more work.

----------Finish for today--------


From henk@ripe.net  Tue Sep 14 04:30:08 2010
Return-Path: <henk@ripe.net>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 895D13A6966 for <ippm@core3.amsl.com>; Tue, 14 Sep 2010 04:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.615
X-Spam-Level: 
X-Spam-Status: No, score=-102.615 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f8P3Z9+sdDVM for <ippm@core3.amsl.com>; Tue, 14 Sep 2010 04:30:04 -0700 (PDT)
Received: from postlady.ripe.net (postlady.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1341]) by core3.amsl.com (Postfix) with ESMTP id C74C13A68E8 for <ippm@ietf.org>; Tue, 14 Sep 2010 04:30:03 -0700 (PDT)
Received: from dodo.ripe.net ([193.0.23.4]) by postlady.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OvTiI-0000CC-89; Tue, 14 Sep 2010 13:30:27 +0200
Received: from [193.0.21.124] (helo=geir.local) by dodo.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OvTiH-0003Ko-EH; Tue, 14 Sep 2010 13:30:13 +0200
Message-ID: <4C8F5CC5.2050304@ripe.net>
Date: Tue, 14 Sep 2010 13:30:13 +0200
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: Henk Uijterwaal <henk@ripe.net>
References: <4C84A31F.5020908@ripe.net>
In-Reply-To: <4C84A31F.5020908@ripe.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5128dcee1263d7b4dd147d614c67a89b4
X-RIPE-Spam-Level: --
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5128dcee1263d7b4dd147d614c67a89b4
Cc: IETF IPPM WG <ippm@ietf.org>
Subject: Re: [ippm] Fwd: WG interest in Multicast performance monitoring drafts
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2010 11:30:08 -0000

IPPM Group,

In Maastricht, Alberto and others presented this set of drafts:

>>> at the upcoming IPPM meeting in Maastricht we will present a draft about
>>> multicast performance monitoring
>>> (draft-bipi-mboned-ip-multicast-pm-requirement-01).
>>> Requirement draft:
>>> http://tools.ietf.org/html/draft-bipi-mboned-ip-multicast-pm-requirement-01
>>> Solution drafts:
>>> http://tools.ietf.org/html/draft-liu-mboned-multicast-realstream-monitor-02
>>> http://tools.ietf.org/html/draft-cociglio-mboned-multicast-pm-00
 
> We would like to know if people consider this topic appropriate for
> the IPPM WG, and if so, if there is interest to work on this topic.

We've received 2 responses to this mail, both confirming that the topic is
interesting but not offering to actually work on it.  That makes it hard
to put this topic on the agenda for the WG at this point in time.  Should
this ever change, we can revisit the situation.

In the meantime, I'd like to ask people who are interested, to at least
read the drafts and send comments to the mboned list and the authors.

Henk



-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
------------------------------------------------------------------------------

I confirm today what I denied yesterday.            Anonymous Politician.

From Ruediger.Geib@telekom.de  Thu Sep 16 07:26:24 2010
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8024C3A68E9 for <ippm@core3.amsl.com>; Thu, 16 Sep 2010 07:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.883
X-Spam-Level: 
X-Spam-Status: No, score=-0.883 tagged_above=-999 required=5 tests=[AWL=-0.048, BAYES_40=-0.185, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ovaQKhQOSb4 for <ippm@core3.amsl.com>; Thu, 16 Sep 2010 07:26:20 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by core3.amsl.com (Postfix) with ESMTP id E50AA3A684F for <ippm@ietf.org>; Thu, 16 Sep 2010 07:26:19 -0700 (PDT)
Received: from s4de8psaanq.blf.telekom.de (HELO S4DE8PSAANQ.mitte.t-com.de) ([10.151.180.166]) by tcmail31.telekom.de with ESMTP; 16 Sep 2010 16:26:41 +0200
Received: from S4DE8PSAAQA.mitte.t-com.de ([10.151.229.12]) by S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 16 Sep 2010 16:26:41 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 16 Sep 2010 16:26:40 +0200
Message-ID: <151C164FE2E066418D8D44D0801543A504B90D51@S4DE8PSAAQA.mitte.t-com.de>
In-Reply-To: <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt - part 3
Thread-Index: ActI5hDf36OqIEzkTBesOmMMqCSfmwABnUUgAJsBURAAlg2kIACAkdzQAEvRcvA=
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net>
From: <Ruediger.Geib@telekom.de>
To: <Barry.Constantine@jdsu.com>
X-OriginalArrivalTime: 16 Sep 2010 14:26:41.0638 (UTC) FILETIME=[2E65C060:01CB55AB]
Cc: ippm@ietf.org
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt - part 3
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 14:26:24 -0000

Hi Barry,

Part 3 of the comments.=20

Regards, Ruediger


-----

Sections 3.1 and 3.2 (MTU, Round Trip and Bandwidth Measurement)

The text does not consider the effect of ECMP (IP load sharing).=20
As soon as Flow Aware Transport (FAT) is deployed, the delays will=20
vary depending on the path taken through the network. If the=20
document doesn't consider the application of ECMP with FAT,=20
please state so explicitely.

I've missed references to RFC 2681 (RTD) and RFC 5136 (network=20
capacity). On the latter, I'd be interested which of the metrics=20
proposed there would determine "bandwidth" in the sense of your=20
draft.

With regard to RTT determination, a reference to RFC 4898 should=20
be included.

Section 3.2

..."Since this=20
   methodology requires that RTT be measured during the entire=20
   throughput test, the extent by which the RTT varied during the=20
   throughput test can be quantified."

I don't recall any prior statement that the RTT must/MUST be=20
measured during the entire test and the metrics suggested don't=20
require RTT measurement. If you want to define an additional=20
metric here, please provide more text and a metric definition.=20
The same applies to section 3.2.2:

  ..."Ideally, the bandwidth test should produce a log output of the=20
   bandwidth achieved across the test interval AND the round trip delay. =
=20

  =20
   And during the actual TCP level performance measurements (Sections
   3.3 - 3.5), the test tool must be able to track round trip time
   of the TCP connection(s) during the test.  Measuring round trip time
   variation (aka "jitter") provides insight into effects of congestive
   delay on the sustained throughput achieved for the TCP layer test."

In addition to an RTT based metric, here you seem to suggest another=20
metric linking RTT and bandwidth measurement.

-----

Section 3.3.1

The diagrams at the end of the section are certainly interesting=20
illustrations, but they may be moved to an appendix.=20

-----

Section 3.3.2 after

..."Dedicated test equipment will generally be required, especially for=20
   line rates of GigE and 10 GigE."

Should you create a measurement load of more than 10% of any provider=20
backbone link bandwidth on a packet based network, you SHOULD agree=20
your testing activity with the network operating center prior to=20
performing these tests.

The same sentence may be added to section 3.4 Traffic management tests,=20
after the same sentence as above.

-----
Section 3.3.2

   "The TCP throughput test should be run over a a long enough duration=20
   to properly exercise network buffers and also characterize
   performance during different time periods of the day.  The results=20
   must be logged at the desired interval and the test must record RTT=20
   and TCP retransmissions at each interval.=20

   This correlation of retransmissions and RTT over the course of the=20
   test will clearly identify which portions of the transfer reached
   TCP Equilbrium state and to what effect increased RTT (congestive
   effects) may have been the cause of reduced equilibrium performance.

   Additionally, the TCP Efficiency and TCP Transfer time metrics should
   be logged in order to further characterize the window size tests."

Please clarify and define in your text, which metrics are of true=20
relevance and which are nice to have. You apply strong requirement=20
language here to capture a metric which isn't defined in your document=20
(retransmission to RTT correlation). The metrics you've defined so far=20
"should be performed additionally". This raises the impression that the
truly required metrics of this document aren't explicitely defined,=20
I think.

-----

Finally, I wonder whether any default settings may be mentioned or=20
approximately validated (you can't always reach them):

- max MTU (should be part of a contract - respect layering aspects)
- access bandwidth (may well be the bottleneck).
- a maximum delay (which may be part of an SLA)
- a default TCP window setting (you mention 64KB)


----------That's it--------


From Barry.Constantine@jdsu.com  Thu Sep 16 18:08:35 2010
Return-Path: <Barry.Constantine@jdsu.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29B0B3A6B9D for <ippm@core3.amsl.com>; Thu, 16 Sep 2010 18:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.675
X-Spam-Level: 
X-Spam-Status: No, score=-5.675 tagged_above=-999 required=5 tests=[AWL=0.924,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SE+pBSJSXTQ2 for <ippm@core3.amsl.com>; Thu, 16 Sep 2010 18:08:32 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by core3.amsl.com (Postfix) with SMTP id 058A23A6AD5 for <ippm@ietf.org>; Thu, 16 Sep 2010 18:08:32 -0700 (PDT)
Received: from source ([209.36.247.245]) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKTJK/pzOA5acEr1E93gOstOyuB5NNiHfK@postini.com; Thu, 16 Sep 2010 18:08:57 PDT
Received: from milexhtca2.ds.jdsu.net ([10.75.2.122]) by Outbound2.jdsu.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 16 Sep 2010 18:02:06 -0700
Received: from MILEXCH1.ds.jdsu.net ([fe80::6444:f010:6d40:bdb]) by milexhtca2.ds.jdsu.net ([::1]) with mapi; Thu, 16 Sep 2010 18:02:06 -0700
From: Barry Constantine <Barry.Constantine@jdsu.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
Date: Thu, 16 Sep 2010 18:02:04 -0700
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt - part 3
Thread-Index: ActI5hDf36OqIEzkTBesOmMMqCSfmwABnUUgAJsBURAAlg2kIACAkdzQAEvRcvABSD070A==
Message-ID: <94DEE80C63F7D34F9DC9FE69E39436BE38BA1DA93A@MILEXCH1.ds.jdsu.net>
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504B90D51@S4DE8PSAAQA.mitte.t-com.de>
In-Reply-To: <151C164FE2E066418D8D44D0801543A504B90D51@S4DE8PSAAQA.mitte.t-com.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Sep 2010 01:02:06.0877 (UTC) FILETIME=[F2CF8CD0:01CB5603]
Cc: "ippm@ietf.org" <ippm@ietf.org>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt - part 3
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 01:08:35 -0000

Hi Rudi,

We really appreciate you taking the time to provide really good comments.

All have been very insightful, especially this last round.

I'll contact you off-list and I would like to schedule time to review all c=
omments.  I think we can more efficiently work through these collaborativel=
y (real-time).

Thanks again,

Barry

=20

Principal Member of Technical Staff

=20

JDSU Communication Test (formerly Acterna)

Emerging Markets and Technology Research        =20

One Milestone Center Court                             =20

Germantown, MD 20876                                        =20

(W) 240-404-2227                                               =20

(C) 301-325-7069


-----Original Message-----
From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]=20
Sent: Thursday, September 16, 2010 10:27 AM
To: Barry Constantine
Cc: ippm@ietf.org
Subject: RE: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt - par=
t 3

Hi Barry,

Part 3 of the comments.=20

Regards, Ruediger


-----

Sections 3.1 and 3.2 (MTU, Round Trip and Bandwidth Measurement)

The text does not consider the effect of ECMP (IP load sharing).=20
As soon as Flow Aware Transport (FAT) is deployed, the delays will=20
vary depending on the path taken through the network. If the=20
document doesn't consider the application of ECMP with FAT,=20
please state so explicitely.

I've missed references to RFC 2681 (RTD) and RFC 5136 (network=20
capacity). On the latter, I'd be interested which of the metrics=20
proposed there would determine "bandwidth" in the sense of your=20
draft.

With regard to RTT determination, a reference to RFC 4898 should=20
be included.

Section 3.2

..."Since this=20
   methodology requires that RTT be measured during the entire=20
   throughput test, the extent by which the RTT varied during the=20
   throughput test can be quantified."

I don't recall any prior statement that the RTT must/MUST be=20
measured during the entire test and the metrics suggested don't=20
require RTT measurement. If you want to define an additional=20
metric here, please provide more text and a metric definition.=20
The same applies to section 3.2.2:

  ..."Ideally, the bandwidth test should produce a log output of the=20
   bandwidth achieved across the test interval AND the round trip delay. =20

  =20
   And during the actual TCP level performance measurements (Sections
   3.3 - 3.5), the test tool must be able to track round trip time
   of the TCP connection(s) during the test.  Measuring round trip time
   variation (aka "jitter") provides insight into effects of congestive
   delay on the sustained throughput achieved for the TCP layer test."

In addition to an RTT based metric, here you seem to suggest another=20
metric linking RTT and bandwidth measurement.

-----

Section 3.3.1

The diagrams at the end of the section are certainly interesting=20
illustrations, but they may be moved to an appendix.=20

-----

Section 3.3.2 after

..."Dedicated test equipment will generally be required, especially for=20
   line rates of GigE and 10 GigE."

Should you create a measurement load of more than 10% of any provider=20
backbone link bandwidth on a packet based network, you SHOULD agree=20
your testing activity with the network operating center prior to=20
performing these tests.

The same sentence may be added to section 3.4 Traffic management tests,=20
after the same sentence as above.

-----
Section 3.3.2

   "The TCP throughput test should be run over a a long enough duration=20
   to properly exercise network buffers and also characterize
   performance during different time periods of the day.  The results=20
   must be logged at the desired interval and the test must record RTT=20
   and TCP retransmissions at each interval.=20

   This correlation of retransmissions and RTT over the course of the=20
   test will clearly identify which portions of the transfer reached
   TCP Equilbrium state and to what effect increased RTT (congestive
   effects) may have been the cause of reduced equilibrium performance.

   Additionally, the TCP Efficiency and TCP Transfer time metrics should
   be logged in order to further characterize the window size tests."

Please clarify and define in your text, which metrics are of true=20
relevance and which are nice to have. You apply strong requirement=20
language here to capture a metric which isn't defined in your document=20
(retransmission to RTT correlation). The metrics you've defined so far=20
"should be performed additionally". This raises the impression that the
truly required metrics of this document aren't explicitely defined,=20
I think.

-----

Finally, I wonder whether any default settings may be mentioned or=20
approximately validated (you can't always reach them):

- max MTU (should be part of a contract - respect layering aspects)
- access bandwidth (may well be the bottleneck).
- a maximum delay (which may be part of an SLA)
- a default TCP window setting (you mention 64KB)


----------That's it--------


From henk@ripe.net  Thu Sep 16 22:32:47 2010
Return-Path: <henk@ripe.net>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 430403A6A83 for <ippm@core3.amsl.com>; Thu, 16 Sep 2010 22:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.614
X-Spam-Level: 
X-Spam-Status: No, score=-102.614 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vd2mkKpuOnp for <ippm@core3.amsl.com>; Thu, 16 Sep 2010 22:32:38 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id 8F0E83A69B5 for <ippm@ietf.org>; Thu, 16 Sep 2010 22:32:37 -0700 (PDT)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OwTZ5-0000SP-W4 for ippm@ietf.org; Fri, 17 Sep 2010 07:33:01 +0200
Received: from [193.0.21.124] (helo=geir.local) by ayeaye.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OwTZ5-00047R-Qg for ippm@ietf.org; Fri, 17 Sep 2010 07:32:51 +0200
Message-ID: <4C92FD83.7050205@ripe.net>
Date: Fri, 17 Sep 2010 07:32:51 +0200
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: IETF IPPM WG <ippm@ietf.org>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------050201080103090100060201"
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5ba998f556aaf5b253211aedda6804f1f
X-RIPE-Spam-Level: --
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5ba998f556aaf5b253211aedda6804f1f
Subject: [ippm] Fwd: FW: NomCom 2010-2011: Call for More Nominations
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 05:32:47 -0000

This is a multi-part message in MIME format.
--------------050201080103090100060201
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Forwarded on request.

-------- Original Message --------
Subject: FW: NomCom 2010-2011: Call for More Nominations
Date: Thu, 16 Sep 2010 19:28:00 -0400
From: Thomas Walsh <twalsh@juniper.net>
To: ietf@ietf.org <ietf@ietf.org>



-----Original Message-----
From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On
Behalf Of NomCom Chair
Sent: Thursday, September 16, 2010 7:26 PM
To: IETF Announcement list
Subject: NomCom 2010-2011: Call for More Nominations



Hi Folks,

Nominations have slowed down dramatically, so this update is to enlist
the community in an effort to pick up the pace.

We are very far behind in nominations for all the open positions but in
particular we need nominations for the IESG and IAOC open positions.
There have been no nominations received (other than for the incumbents)
in INT, RAI, and RTG, and only 1 for OPS.  Likewise, in IAOC there have
been no nominations submitted other than the incumbent.

The acceptance rates of those nominated has also been very slow. In
order to initiate the open list of willing nominees we are in need of a
reasonable number of acceptances, and due to the low number of nominees
and acceptances have delayed the start date for publishing the first
open list to September 20.  So if you have been nominated and are
willing to serve, but have not yet confirmed this by email back to the
NomCom, please do so as soon as possible.

We need Community input and participation! We cannot properly execute
the task of selecting the best candidates for these positions with so
few nominations and acceptances. So, please consider making
nominations for the open positions, in particular those for which we
have so few nominations � it takes just a few minutes of your time.
Right now, we just need the names/email addresses.

Why do we need more nominations?  Well, even if you think a willing
incumbent is doing a very good job and should be returned, his or her
ability to serve again might be impacted by unforeseen circumstances
between now and March. NomCom needs to consider multiple nominees to be
prepared in the event one or more candidates is unable to serve come next
March and to ensure we have chosen the best candidate.

There are several ways you can help the IETF Nominating Committee.

- You may nominate yourself.
- You can nominate someone you know whom you think would do a good job.

Do not worry about whether they might already be nominated. We would
much prefer to receive the same nomination several times rather than
miss a good person we should consider.

How to submit Nominations:
--------------------------
The list of positions we need to fill, and the provided Job
Descriptions, and forms for nominations, can be found in the call for
nominations at: https://datatracker.ietf.org/ann/nomcom/2468/

You may enter a nomination by going to the following URL
https://wiki.tools.ietf.org/group/nomcom/10/nominate

You may also nominate someone by sending an email to nomcom10@ietf.org
and giving us their name, email address and the open position you are
nominating them for. We will take care of the rest.

If you are asked for a user name and password, use an existing ietf login
and password. If you need a login and password, request one from the tools
page at the following URL http://trac.tools.ietf.org/newlogin


Open List:
----------
As you already know, NomCom 2010-2011 will follow the policy for "Open
Disclosure of Willing Nominees" described in RFC 5680.

Feedback Collection:
--------------------
Once the open list is available, the entire community will be invited
to provide feedback. I will send a further announcement requesting
feedback on the nominees, describing how to submit feedback, and how to
view the open list of nominees.

Thank you,

Thomas Walsh
Chair, NomCom 2010-2011
nomcom-chair@ietf.org
twalsh@juniper.net




--------------050201080103090100060201
Content-Type: text/plain;
 name="ATT00001..txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="ATT00001..txt"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCklFVEYt
QW5ub3VuY2UgbWFpbGluZyBsaXN0DQpJRVRGLUFubm91bmNlQGlldGYub3JnDQpodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lldGYtYW5ub3VuY2UNCg==
--------------050201080103090100060201
Content-Type: text/plain;
 name="Attached Message Part"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="Attached Message Part"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KSWV0ZiBt
YWlsaW5nIGxpc3QKSWV0ZkBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL2lldGYKCg==
--------------050201080103090100060201--

From henk@ripe.net  Mon Sep 20 00:34:24 2010
Return-Path: <henk@ripe.net>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5ED483A68DA for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 00:34:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.607
X-Spam-Level: 
X-Spam-Status: No, score=-102.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gitiex6IOS1F for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 00:34:21 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id 3AB173A6979 for <ippm@ietf.org>; Mon, 20 Sep 2010 00:34:20 -0700 (PDT)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OxatZ-00066D-LP for ippm@ietf.org; Mon, 20 Sep 2010 09:34:43 +0200
Received: from [193.0.21.124] (helo=guest-57.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OxatZ-0000yz-HZ for ippm@ietf.org; Mon, 20 Sep 2010 09:34:37 +0200
Message-ID: <4C970E8D.6010909@ripe.net>
Date: Mon, 20 Sep 2010 09:34:37 +0200
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: ippm@ietf.org
References: <4C7CBBFD.1030402@ripe.net>
In-Reply-To: <4C7CBBFD.1030402@ripe.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5105115759653a638dc51d5b6120b2066
X-RIPE-Spam-Level: --
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5105115759653a638dc51d5b6120b2066
Subject: Re: [ippm] End of WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 07:34:24 -0000

IPPM group,

On 31/08/2010 10:23, Henk Uijterwaal wrote:
> IPPM Group,
> 
> This is a Working Group Last Call for the draft:
> 
>     TCP Throughput Testing Methodology
>     draft-ietf-ippm-tcp-throughput-tm-06.txt
> 
> This version of the draft addresses all issues brought up on the list and
> at the Maastricht meeting.  It also fixes a number of ID-nits.  The authors
> believe that no further work on the draft is needed.  Note that there are
> a few spelling mistakes in the draft, these will be fixed when including
> any other LC comments.
> 
> Please review the draft and raise any issues by Monday, September 20,
> 9:00 UTC.  An URL for the draft is:
> 
>     http://www.ietf.org/id/draft-ietf-ippm-tcp-throughput-tm-06.txt

A number of issues have been raised, which makes it hard to declare
consensus on this document.  The authors are invited to submit
a new draft.  This will be followed by a short second WGLC to make
sure that all issues have been addressed.

Matt & Henk.

-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
------------------------------------------------------------------------------

I confirm today what I denied yesterday.            Anonymous Politician.

From Barry.Constantine@jdsu.com  Mon Sep 20 05:04:56 2010
Return-Path: <Barry.Constantine@jdsu.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C1233A68CC for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 05:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.752
X-Spam-Level: 
X-Spam-Status: No, score=-5.752 tagged_above=-999 required=5 tests=[AWL=0.847,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kob6hVPRKJmD for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 05:04:55 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by core3.amsl.com (Postfix) with SMTP id 0D3C03A689D for <ippm@ietf.org>; Mon, 20 Sep 2010 05:04:53 -0700 (PDT)
Received: from source ([209.36.247.244]) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKTJdN/baez1kSjak9Dh4RZh751yYcV14F@postini.com; Mon, 20 Sep 2010 05:05:19 PDT
Received: from milexhtca2.ds.jdsu.net ([10.75.2.122]) by Outbound1.jdsu.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 20 Sep 2010 05:05:13 -0700
Received: from MILEXCH1.ds.jdsu.net ([fe80::6444:f010:6d40:bdb]) by milexhtca2.ds.jdsu.net ([::1]) with mapi; Mon, 20 Sep 2010 05:05:13 -0700
From: Barry Constantine <Barry.Constantine@jdsu.com>
To: Henk Uijterwaal <henk@ripe.net>, "ippm@ietf.org" <ippm@ietf.org>
Date: Mon, 20 Sep 2010 05:03:50 -0700
Thread-Topic: [ippm] End of WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
Thread-Index: ActYllChMBrSBpx/SROtPUKK+Y1iuwAJZLUv
Message-ID: <94DEE80C63F7D34F9DC9FE69E39436BE38B92A1A13@MILEXCH1.ds.jdsu.net>
References: <4C7CBBFD.1030402@ripe.net>,<4C970E8D.6010909@ripe.net>
In-Reply-To: <4C970E8D.6010909@ripe.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Sep 2010 12:05:13.0903 (UTC) FILETIME=[14F72BF0:01CB58BC]
Subject: Re: [ippm] End of WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 12:04:56 -0000

That makes sense Henk.

We're going to work on this directly with Rudi Geib (majority of comments) =
and hope to have new draft available sometime this week.

Thanks,
Barry

________________________________________
From: ippm-bounces@ietf.org [ippm-bounces@ietf.org] On Behalf Of Henk Uijte=
rwaal [henk@ripe.net]
Sent: Monday, September 20, 2010 3:34 AM
To: ippm@ietf.org
Subject: Re: [ippm] End of WGLC for draft-ietf-ippm-tcp-throughput-tm-06.tx=
t

IPPM group,

On 31/08/2010 10:23, Henk Uijterwaal wrote:
> IPPM Group,
>
> This is a Working Group Last Call for the draft:
>
>     TCP Throughput Testing Methodology
>     draft-ietf-ippm-tcp-throughput-tm-06.txt
>
> This version of the draft addresses all issues brought up on the list and
> at the Maastricht meeting.  It also fixes a number of ID-nits.  The autho=
rs
> believe that no further work on the draft is needed.  Note that there are
> a few spelling mistakes in the draft, these will be fixed when including
> any other LC comments.
>
> Please review the draft and raise any issues by Monday, September 20,
> 9:00 UTC.  An URL for the draft is:
>
>     http://www.ietf.org/id/draft-ietf-ippm-tcp-throughput-tm-06.txt

A number of issues have been raised, which makes it hard to declare
consensus on this document.  The authors are invited to submit
a new draft.  This will be followed by a short second WGLC to make
sure that all issues have been addressed.

Matt & Henk.

--
---------------------------------------------------------------------------=
---
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.ne=
t
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
---------------------------------------------------------------------------=
---

I confirm today what I denied yesterday.            Anonymous Politician.
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm=

From acmorton@att.com  Mon Sep 20 05:06:47 2010
Return-Path: <acmorton@att.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 709213A6936 for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 05:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.232
X-Spam-Level: 
X-Spam-Status: No, score=-104.232 tagged_above=-999 required=5 tests=[AWL=-1.036, BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3iDO2mDrAC2e for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 05:06:45 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with ESMTP id B70C13A689D for <ippm@ietf.org>; Mon, 20 Sep 2010 05:06:45 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-13.tower-120.messagelabs.com!1284984428!46719416!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 18677 invoked from network); 20 Sep 2010 12:07:09 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-13.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Sep 2010 12:07:09 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o8KC6Ze8007765 for <ippm@ietf.org>; Mon, 20 Sep 2010 08:06:35 -0400
Received: from klpd017.kcdc.att.com (klpd017.kcdc.att.com [135.188.40.86]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o8KC6VLS007707 for <ippm@ietf.org>; Mon, 20 Sep 2010 08:06:31 -0400
Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klpd017.kcdc.att.com (8.14.4/8.14.4) with ESMTP id o8KC74tM013816 for <ippm@ietf.org>; Mon, 20 Sep 2010 07:07:04 -0500
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by klpd017.kcdc.att.com (8.14.4/8.14.4) with ESMTP id o8KC6viF013741 for <ippm@ietf.org>; Mon, 20 Sep 2010 07:06:58 -0500
Message-Id: <201009201206.o8KC6viF013741@klpd017.kcdc.att.com>
Received: from acmt.att.com (ds135-16-251-236.dhcps.ugn.att.com[135.16.251.236](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20100920120656gw100ei144e>; Mon, 20 Sep 2010 12:06:57 +0000
X-Originating-IP: [135.16.251.236]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 20 Sep 2010 08:07:18 -0400
To: Henk Uijterwaal <henk@ripe.net>, "ippm@ietf.org" <ippm@ietf.org>
From: Al Morton <acmorton@att.com>
In-Reply-To: <7.1.0.9.0.20100910100644.033b3fe0@att.com>
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504B0DFD9@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38BA05AE77@MILEXCH1.ds.jdsu.net> <7.1.0.9.0.20100910100644.033b3fe0@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Barry Constantine <Barry.Constantine@jdsu.com>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 12:06:47 -0000

Henk, IPPM,

Henk wrote:
 > Please review the draft and raise any issues by Monday, September 20,
 > 9:00 UTC.  An URL for the draft is:
 >
 >     http://www.ietf.org/id/draft-ietf-ippm-tcp-throughput-tm-06.txt

I didn't remember the 9:00 UTC aspect, just that the 20th was the
deadline...

I have the following comments on  *-ippm-tcp-throughput-tm-06.txt
(written on the plane yesterday, so at least they were prepared on time).
There may be some overlap with earlier comments, I didn't have access
to all of them while reading.

Al

S1 - Intro

p1 current text:
>    Testing an operational network prior to customer activation is
>    referred to as "turn-up" testing and the SLA (Service Level
>    Agreement) is generally based upon Layer 2/3 packet throughput,
>    delay, loss and jitter.

I don't think this methodology can be the basis for SLA on throughput,
even TCP throughput, because of the many reasons for variability in
the results and the fact that IPPM is not writing standards track metrics
in this draft. I have further comments along these lines, but it would
suffice to replace throughput with information rate for now.
Other suggested edits below:

NEW:
    Testing an operational network prior to customer activation is
    referred to as "turn-up" testing and the SLA (Service Level
    Agreement) is generally based upon Layer 2/3 information rate,
    packet delay, loss and delay variation.      ^^^^^^^^^^^^^^^^^
    ^^^^^^                 ^^^^^^^^^^^^^^^^

-------------------------------------------------------------------------
p7 current text:

>    One other important note, it is highly recommended that traditional
>    Layer 2/3 type tests are conducted to verify the integrity of the
>    network before conducting TCP tests.  Examples include RFC 2544
>    [RFC2544], iperf (UDP mode), or manual packet layer test techniques
>    where packet throughput, loss, and delay measurements are conducted.

There is definitely a need for this phase of testing, and I support
including this paragraph in the draft.

However, IPPM needs to be very careful with the wording here, because:

- RFC 2544 has been applied well-beyond its intended scope for
   operational service turn-up testing.  RFC 2544 is lab-use only.

It's a problem when there's a need, but no standard.
RFC 2544-like methods were applied to fill the gap.
And we've got that situation now with many manufacturers
pointing to RFC 2544 and doing something 2544-like, but not
really embracing the scope of 2544 procedures (they only work
reliably in the lab - the live network is different/wilder animal).
There is an effort intended to address the Service Activation
Test methodology in the Ethernet Services space, ITU-T Y.156sam,
a work in progress in Question 17 of Study Group 12.

Also, IETF working groups and the IESG will certainly respect the
scope of other RFCs and BMWG's scope in particular, because
if BMWG methods were let loose on networks, congestion and
other bad scenarios will result (especially without the built-in
safety net that BMWG provided - a testing-only address space that
routers can always drop if they see it).

So I suggest the following wording:
NEW:
    One other important note, it is highly recommended that traditional
    Layer 2/3 type tests are conducted to verify the integrity of the
    network before conducting TCP tests.  Examples include iperf (UDP mode)
    and manual packet layer test techniques
    where packet throughput, loss, and delay measurements are conducted.
    When available, standardized testing similar to RFC 2544 [RFC2544] but
    adapted for use on operational networks may be used (because RFC 2544
    methods are not intended for use outside the lab environment).

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

S2
OLD
2. Goals of this Methodology
suggest NEW
2. Scope and Goals of this Methodology

OLD
>    Before defining the goals of this methodology, it is important to
>    clearly define the areas that are not intended to be measured or
>    analyzed by such a methodology.
suggest NEW
    Before defining the goals of this methodology, it is important to
    clearly define the areas that are out-of-scope for this
    methodology.

suggest additional out-of-scope item:

The methodology is not intended to measure TCP throughput as part of a
SLA, or to compare the TCP performance between service providers or
to compare between implementations of this methodology (test equipment).

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


2.2 Metrics for TCP Throughput Tests
...
>    The TCP Transfer time can also be used to provide a normalized ratio
>    of the actual TCP Transfer Time versus ideal Transfer Time.  This
>    ratio is called the TCP Transfer Index and is defined as:
>
>                      Actual TCP Transfer Time
>                     -------------------------
>                      Ideal TCP Transfer Time

There' no definition of "Ideal TCP Transfer Time", but I conclude from
the paragraph below that it is the theoretical raw capacity combined
with a block of information that needs to be transferred.  Since there's
no flow control/ARQ at all, I would be more comfortable calling the
denominator "Ideal Transfer Time", or "Theoretical Transfer Time".

It would also seem appropriate to explain to the user that no TCP
will ever achieve the same performance as Theoretical, and perhaps
this means we are comparing apples and oranges in this metric...


>    An example would be the bulk transfer of 100 MB upon 5 simultaneous
>    TCP connections over a 500 Mbit/s Ethernet service

Is this the Committed Information Rate (CIR) of the Ethernet Service?

>                                                      (each connection
>    uploading 100 MB).  Each connection may achieve different throughputs
>    during a test and the overall throughput rate is not always easy to
>    determine (especially as the number of connections increases).

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

3. TCP Throughput Testing Methodology
...
>    2. Baseline

(Average?)

>Round-trip Delay and

Raw capacity (without TCP flow control).

>      . These measurements
>    provide estimates of the ideal TCP window size, which will be used in
>    subsequent test steps.

-----------------------------------------------------------------------------
(later, S3)

>    - TCP implementation used by the test host

and the OS version number,

>  i.e. Linux OS kernel

2.6.......

>    using TCP Reno, TCP options supported, etc.  This will obviously be
>    more important when using custom test equipment where the TCP
>    implementation may be customized or tuned to run in higher
>    performance hardware
>
>
>    - Most importantly, the TCP test host must be capable of generating
>    and receiving stateful TCP test traffic at the full link speed of the
>    network under test. As a general rule of thumb, testing TCP
>    throughput at rates greater than 100 Mbit/sec generally requires high
>    performance server hardware or dedicated hardware based test tools.

(add)
     Thus, other devices cannot realize higher TCP throughput, and user
     expectations SHOULD be set accordingly with user manual or notes on
     the results report.


>    - To measure RTT and TCP Efficiency per connection, this will



At 10:13 AM 9/10/2010, Al Morton wrote:
>Barry, Rudi,
>
>My recollection from the March IPPM session is that
>  - we agreed to take this up as an Informational RFC
>  - we aren't defining metrics here
>   (if we were, it would be standards track)
>
>So, I agree with the "Framework" title change.
>I would clarify that "Type-P" metric specifications
>are un-attempted with this scope (what the draft does now).
>
>I will hopefully add some more comments later today (sigh).
>
>regards,
>Al
>
>At 09:44 AM 9/10/2010, Barry Constantine wrote:
>>...
>>I thought we agreed that if this were to be retitled a framework 
>>(and informational versus a standard), then the Type P metrics 
>>could remain unaddressed.
>>
>>Please let me know if I am misunderstanding, will definitely 
>>incorporate your comments in this email (minus the Type P metric work).
>>
>>
>>Thanks,
>>
>>Barry
>>
>>


From henk@ripe.net  Mon Sep 20 06:32:53 2010
Return-Path: <henk@ripe.net>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FFB13A6A6E for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 06:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.606
X-Spam-Level: 
X-Spam-Status: No, score=-102.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kG7QIQVyti1B for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 06:32:52 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id 04F6C3A6A63 for <ippm@ietf.org>; Mon, 20 Sep 2010 06:32:52 -0700 (PDT)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OxgUR-00023G-JN; Mon, 20 Sep 2010 15:33:12 +0200
Received: from [193.0.21.124] (helo=guest-57.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1OxgUR-0003d5-BB; Mon, 20 Sep 2010 15:33:03 +0200
Message-ID: <4C97628F.5070308@ripe.net>
Date: Mon, 20 Sep 2010 15:33:03 +0200
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: Al Morton <acmorton@att.com>
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504B0DFD9@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38BA05AE77@MILEXCH1.ds.jdsu.net> <7.1.0.9.0.20100910100644.033b3fe0@att.com> <201009201206.o8KC6vkT013740@klpd017.kcdc.att.com>
In-Reply-To: <201009201206.o8KC6vkT013740@klpd017.kcdc.att.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5022e04aeead8e6c18f7fbf7f1a7d6264
X-RIPE-Spam-Level: --
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5022e04aeead8e6c18f7fbf7f1a7d6264
Cc: Barry Constantine <Barry.Constantine@jdsu.com>, "ippm@ietf.org" <ippm@ietf.org>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 13:32:53 -0000

On 20/09/2010 14:07, Al Morton wrote:
> Henk, IPPM,
> 
> Henk wrote:
>> Please review the draft and raise any issues by Monday, September 20,
>> 9:00 UTC.  An URL for the draft is:
>>
>>     http://www.ietf.org/id/draft-ietf-ippm-tcp-throughput-tm-06.txt
> 
> I didn't remember the 9:00 UTC aspect, just that the 20th was the
> deadline...

You're only a few hours late, so I suggest that we include these
comments as well.

Henk



-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
------------------------------------------------------------------------------

I confirm today what I denied yesterday.            Anonymous Politician.

From Barry.Constantine@jdsu.com  Mon Sep 20 06:41:06 2010
Return-Path: <Barry.Constantine@jdsu.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 08F883A6A6D for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 06:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.817
X-Spam-Level: 
X-Spam-Status: No, score=-5.817 tagged_above=-999 required=5 tests=[AWL=0.782,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZavDcxfu8+m for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 06:40:51 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by core3.amsl.com (Postfix) with SMTP id 0966A3A6AA1 for <ippm@ietf.org>; Mon, 20 Sep 2010 06:40:22 -0700 (PDT)
Received: from source ([209.36.247.244]) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKTJdkV/q/XrrpBBJFBZ++r9ZwxezRDa1X@postini.com; Mon, 20 Sep 2010 06:40:48 PDT
Received: from milexhtca2.ds.jdsu.net ([10.75.2.122]) by Outbound1.jdsu.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 20 Sep 2010 06:39:42 -0700
Received: from MILEXCH1.ds.jdsu.net ([fe80::6444:f010:6d40:bdb]) by milexhtca2.ds.jdsu.net ([::1]) with mapi; Mon, 20 Sep 2010 06:39:42 -0700
From: Barry Constantine <Barry.Constantine@jdsu.com>
To: Henk Uijterwaal <henk@ripe.net>, Al Morton <acmorton@att.com>
Date: Mon, 20 Sep 2010 06:39:40 -0700
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
Thread-Index: ActYyGI6pPkxpp25Rg6cUqIvl04JPgAANnwg
Message-ID: <94DEE80C63F7D34F9DC9FE69E39436BE38BA28BAF2@MILEXCH1.ds.jdsu.net>
References: <4C7CBBFD.1030402@ripe.net> <151C164FE2E066418D8D44D0801543A5049C88F8@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9F4E14F@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504A56E4D@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38B9FF2C81@MILEXCH1.ds.jdsu.net> <151C164FE2E066418D8D44D0801543A504B0DFD9@S4DE8PSAAQA.mitte.t-com.de> <94DEE80C63F7D34F9DC9FE69E39436BE38BA05AE77@MILEXCH1.ds.jdsu.net> <7.1.0.9.0.20100910100644.033b3fe0@att.com> <201009201206.o8KC6vkT013740@klpd017.kcdc.att.com> <4C97628F.5070308@ripe.net>
In-Reply-To: <4C97628F.5070308@ripe.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Sep 2010 13:39:42.0404 (UTC) FILETIME=[47A7C840:01CB58C9]
Cc: "ippm@ietf.org" <ippm@ietf.org>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 13:41:06 -0000

Absolutely fine.

Thanks,

Barry

=20

-----Original Message-----
From: Henk Uijterwaal [mailto:henk@ripe.net]=20
Sent: Monday, September 20, 2010 9:33 AM
To: Al Morton
Cc: ippm@ietf.org; Barry Constantine
Subject: Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

On 20/09/2010 14:07, Al Morton wrote:
> Henk, IPPM,
>=20
> Henk wrote:
>> Please review the draft and raise any issues by Monday, September 20,
>> 9:00 UTC.  An URL for the draft is:
>>
>>     http://www.ietf.org/id/draft-ietf-ippm-tcp-throughput-tm-06.txt
>=20
> I didn't remember the 9:00 UTC aspect, just that the 20th was the
> deadline...

You're only a few hours late, so I suggest that we include these
comments as well.

Henk



--=20
---------------------------------------------------------------------------=
---
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.ne=
t
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
---------------------------------------------------------------------------=
---

I confirm today what I denied yesterday.            Anonymous Politician.

From nspring@cs.umd.edu  Mon Sep 20 08:16:26 2010
Return-Path: <nspring@cs.umd.edu>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FFA73A6817 for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 08:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.078
X-Spam-Level: **
X-Spam-Status: No, score=2.078 tagged_above=-999 required=5 tests=[BAYES_50=0.001, SUBJ_ALL_CAPS=2.077]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cHwOVjzj4Ef3 for <ippm@core3.amsl.com>; Mon, 20 Sep 2010 08:16:24 -0700 (PDT)
Received: from bacon.cs.umd.edu (router-304.cs.umd.edu [128.8.127.145]) by core3.amsl.com (Postfix) with ESMTP id 721BA3A68E1 for <ippm@ietf.org>; Mon, 20 Sep 2010 08:16:24 -0700 (PDT)
X-CSD-MailScanner-Watermark: 1285600603.09946@DmwwEi5iwErqhXHUho+ZWg
Received: from kohoutek.cs.umd.edu (kohoutek.cs.umd.edu [128.8.126.123]) (authenticated bits=0) by bacon.cs.umd.edu (8.13.1/8.14.1) with ESMTP id o8KFGXsT022804 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ippm@ietf.org>; Mon, 20 Sep 2010 11:16:41 -0400
Message-Id: <1D82DE04-77E0-486D-8059-5F5925A7DAD0@cs.umd.edu>
From: Neil Spring <nspring@cs.umd.edu>
To: ippm@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 20 Sep 2010 11:16:36 -0400
X-Mailer: Apple Mail (2.936)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (bacon.cs.umd.edu [172.24.3.34]); Mon, 20 Sep 2010 11:16:42 -0400 (EDT)
X-CSD-Milter-Status: Skipped o8KFGXsT022804 on bacon (user authenticated to SMTP server)
X-CSD-MailScanner-Information: Please email staff@cs.umd.edu for more information
X-MailScanner-ID: o8KFGXsT022804
X-CSD-MailScanner: Found to be clean
X-CSD-MailScanner-SpamCheck: not spam, SpamAssassin (cached, score=-47.923, required 5, ALL_TRUSTED -50.00, SUBJ_ALL_CAPS 2.08)
X-CSD-MailScanner-From: nspring@cs.umd.edu
X-Mailman-Approved-At: Tue, 21 Sep 2010 08:01:26 -0700
Subject: [ippm] PAM 2011 CFP
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 15:16:26 -0000

Call for Papers
Passive and Active Measurement Conference (PAM) 2011
Atlanta, GA, USA
Conference Web: http://pam2011.gatech.edu/
Submissions: http://pam11.cs.umd.edu/

The 12th Passive and Active Measurement conference will be held March  
20-22nd, 2011 in Atlanta. PAM focuses on research and practical  
applications of network measurement and analysis techniques. The  
conference's goal is to provide a forum for current work in its early  
stages. Original papers are invited from the research and operations  
communities on topics including, but not limited to:

	* Active Network Measurements
	* Passive Network Measurements
	* Performance Metrics
	* Traffic Statistics
	* Measurement Visualization
	* New Measurement Approaches & Techniques
	* Deployment of Measurement Infrastructure
	* New Measurement Initiatives
	* Applications of Network Measurements
	* Network Measurements and Security
	* Network Troubleshooting using Measurements
	* Reproduce (or Refute) Previous Measurement Results
The PAM steering committee believes that releasing measurement data  
allows for better science to be conducted in the field of network  
measurement. Therefore, an award will be given at PAM 2011 for the  
best paper based on a new dataset that the authors are releasing for  
community use in subsequent research. To qualify, a paper must  
significantly utilize a dataset that has been collected for the work  
presented in the paper. Further, the dataset must be freely available  
to any researcher; wireless data sets may, for instance, be published  
through CRAWDAD. Authors should flag papers they wish to be considered  
for this award with a footnote on the first page of the paper. Novel  
datasets are especially encouraged. The awarded paper will be chosen  
from the set of qualifying papers accepted for the conference by a  
committee made up of a subset of the program and steering committees.

Important Dates
	* Abstract Registration: October 2, 2010 23:59pm GMT (UK Time)
	* Paper Submission: October 9, 2010 23:59pm GMT (UK Time)
	* Conference: March 20-22, 2011

Conference Organizers

General Chair: George Riley, Georgia Institute of Technology
Program Chair: Neil Spring, University of Maryland

Program Committee

Nevil Brownlee, University of Auckland
kc claffy, CAIDA
Benoit Donnet, Laboratoire d'Informatique de Paris 6
Constantine Dovrolis, Georgia Tech
Mehmet Gunes, University of Nevada, Reno
Gianluca Iannaccone, Intel Research
Arvind Krisnamurthy, University of Washington
Aleksandar Kuzmanovic, Northwestern University
Sridhar Machiraju, Google
Alan Mislove, Northeastern University
Ricardo Oliveira, Thousandeyes
Dina Papagiannaki, Intel Research
George Riley, Georgia Tech
Eve Schooler, Intel Research
Rob Sherwood, Deutsche Telekom Inc. R&D Lab
Fernando Silveira, Technicolor
Joel Sommers, Colgate University
Oliver Spatschek, AT&T Labs -- Research
Nina Taft, Intel Research
Arun Venkataramani, University of Massachusetts
Walter Willinger, AT&T Labs -- Research



_______________________________________________
IMRG mailing list
IMRG@irtf.org
https://www.irtf.org/mailman/listinfo/imrg

From Barry.Constantine@jdsu.com  Fri Sep 24 05:11:28 2010
Return-Path: <Barry.Constantine@jdsu.com>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 587893A6B82 for <ippm@core3.amsl.com>; Fri, 24 Sep 2010 05:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.873
X-Spam-Level: 
X-Spam-Status: No, score=-5.873 tagged_above=-999 required=5 tests=[AWL=0.726,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NLk9oQXV7gY4 for <ippm@core3.amsl.com>; Fri, 24 Sep 2010 05:11:24 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by core3.amsl.com (Postfix) with SMTP id 36BB93A6B4B for <ippm@ietf.org>; Fri, 24 Sep 2010 05:11:22 -0700 (PDT)
Received: from source ([209.36.247.245]) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKTJyViHGqEfUt3UNV76w8+fCcX6pPc+S9@postini.com; Fri, 24 Sep 2010 05:11:55 PDT
Received: from milexhtca1.ds.jdsu.net ([10.75.2.121]) by Outbound2.jdsu.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 24 Sep 2010 05:06:20 -0700
Received: from MILEXCH1.ds.jdsu.net ([fe80::6444:f010:6d40:bdb]) by milexhtca1.ds.jdsu.net ([::1]) with mapi; Fri, 24 Sep 2010 05:06:20 -0700
From: Barry Constantine <Barry.Constantine@jdsu.com>
To: Henk Uijterwaal <henk@ripe.net>, "ippm@ietf.org" <ippm@ietf.org>
Date: Fri, 24 Sep 2010 05:06:19 -0700
Thread-Topic: [ippm] End of WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
Thread-Index: ActYllChMBrSBpx/SROtPUKK+Y1iuwDSiZvQ
Message-ID: <94DEE80C63F7D34F9DC9FE69E39436BE38BA374A0C@MILEXCH1.ds.jdsu.net>
References: <4C7CBBFD.1030402@ripe.net> <4C970E8D.6010909@ripe.net>
In-Reply-To: <4C970E8D.6010909@ripe.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 24 Sep 2010 12:06:20.0585 (UTC) FILETIME=[E65D0990:01CB5BE0]
Subject: Re: [ippm] End of WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 12:11:29 -0000

Hello,

The new draft-07 version has been posted which incorporated all comments re=
ceived during the WGLC.

Thanks to Rudi, Henk, and Al for providing excellent comments.


Barry



-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of Hen=
k Uijterwaal
Sent: Monday, September 20, 2010 3:35 AM
To: ippm@ietf.org
Subject: Re: [ippm] End of WGLC for draft-ietf-ippm-tcp-throughput-tm-06.tx=
t

IPPM group,

On 31/08/2010 10:23, Henk Uijterwaal wrote:
> IPPM Group,
>=20
> This is a Working Group Last Call for the draft:
>=20
>     TCP Throughput Testing Methodology
>     draft-ietf-ippm-tcp-throughput-tm-06.txt
>=20
> This version of the draft addresses all issues brought up on the list and
> at the Maastricht meeting.  It also fixes a number of ID-nits.  The autho=
rs
> believe that no further work on the draft is needed.  Note that there are
> a few spelling mistakes in the draft, these will be fixed when including
> any other LC comments.
>=20
> Please review the draft and raise any issues by Monday, September 20,
> 9:00 UTC.  An URL for the draft is:
>=20
>     http://www.ietf.org/id/draft-ietf-ippm-tcp-throughput-tm-06.txt

A number of issues have been raised, which makes it hard to declare
consensus on this document.  The authors are invited to submit
a new draft.  This will be followed by a short second WGLC to make
sure that all issues have been addressed.

Matt & Henk.

--=20
---------------------------------------------------------------------------=
---
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.ne=
t
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
---------------------------------------------------------------------------=
---

I confirm today what I denied yesterday.            Anonymous Politician.
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm

From root@core3.amsl.com  Fri Sep 24 05:15:04 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ippm@ietf.org
Delivered-To: ippm@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 710823A6997; Fri, 24 Sep 2010 05:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100924121503.710823A6997@core3.amsl.com>
Date: Fri, 24 Sep 2010 05:15:02 -0700 (PDT)
Cc: ippm@ietf.org
Subject: [ippm] I-D Action:draft-ietf-ippm-tcp-throughput-tm-07.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 12:15:04 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP Performance Metrics Working Group of the IETF.


	Title           : Framework for TCP Throughput Testing
	Author(s)       : B. Constantine, et al.
	Filename        : draft-ietf-ippm-tcp-throughput-tm-07.txt
	Pages           : 23
	Date            : 2010-09-24

This document describes a framework for measuring sustained TCP 
throughput performance in an end-to-end managed network environment.  
This document is intended to provide a practical methodology to help 
users validate the TCP layer performance of a managed network, which
should provide a better indication of end-user experience.  In the 
framework, various TCP and network parameters are identified that 
should be tested as part of the network verification at the TCP 
layer.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ippm-tcp-throughput-tm-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ippm-tcp-throughput-tm-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From henk@ripe.net  Fri Sep 24 05:40:39 2010
Return-Path: <henk@ripe.net>
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A17AD3A6B85 for <ippm@core3.amsl.com>; Fri, 24 Sep 2010 05:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BkzXnKGL9ZSu for <ippm@core3.amsl.com>; Fri, 24 Sep 2010 05:40:38 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id 526273A6B6C for <ippm@ietf.org>; Fri, 24 Sep 2010 05:40:38 -0700 (PDT)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <henk@ripe.net>) id 1Oz7aI-0002uH-HJ; Fri, 24 Sep 2010 14:41:08 +0200
Received: from [193.0.21.124] (helo=guest-81.ripe.net) by dodo.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1Oz7aI-0005Dx-97; Fri, 24 Sep 2010 14:41:02 +0200
Message-ID: <4C9C9C5E.6070606@ripe.net>
Date: Fri, 24 Sep 2010 14:41:02 +0200
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Barry Constantine <Barry.Constantine@jdsu.com>
References: <4C7CBBFD.1030402@ripe.net> <4C970E8D.6010909@ripe.net> <94DEE80C63F7D34F9DC9FE69E39436BE38BA374A0C@MILEXCH1.ds.jdsu.net>
In-Reply-To: <94DEE80C63F7D34F9DC9FE69E39436BE38BA374A0C@MILEXCH1.ds.jdsu.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d563f52a684f359c72e42f38cd8e448561
X-RIPE-Spam-Level: --
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d563f52a684f359c72e42f38cd8e448561
Cc: "ippm@ietf.org" <ippm@ietf.org>
Subject: Re: [ippm] End of WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 12:40:39 -0000

Barry,

> The new draft-07 version has been posted which incorporated all comments received during the WGLC.
> 
> Thanks to Rudi, Henk, and Al for providing excellent comments.

Thanks, we'll start a second WGLC soon.

Henk




-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
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
------------------------------------------------------------------------------

I confirm today what I denied yesterday.            Anonymous Politician.
