Re: [ippm] WGLC for draft-ietf-ippm-tcp-throughput-tm-06.txt

Barry Constantine <Barry.Constantine@jdsu.com> Mon, 13 September 2010 13:19 UTC

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. comments and will incorporate this into the final draft.

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

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