Re: [ippm] My comments on draft-ietf-ippm-testplan-rfc2680-03

"MORTON, ALFRED C (AL)" <acmorton@att.com> Wed, 16 October 2013 17:32 UTC

Return-Path: <acmorton@att.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC79421F99F3 for <ippm@ietfa.amsl.com>; Wed, 16 Oct 2013 10:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UjxOgUbG+g5k for <ippm@ietfa.amsl.com>; Wed, 16 Oct 2013 10:32:48 -0700 (PDT)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [192.20.225.111]) by ietfa.amsl.com (Postfix) with ESMTP id AAAB411E8192 for <ippm@ietf.org>; Wed, 16 Oct 2013 10:32:44 -0700 (PDT)
Received: from mail-azure.research.att.com (unknown [135.207.255.18]) by mail-pink.research.att.com (Postfix) with ESMTP id D573F122BDE; Wed, 16 Oct 2013 13:27:25 -0400 (EDT)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.178.11]) by mail-azure.research.att.com (Postfix) with ESMTP id E1E55E3023; Wed, 16 Oct 2013 13:27:24 -0400 (EDT)
Received: from njfpsrvexg8.research.att.com (unknown [135.207.255.242]) by mail-blue.research.att.com (Postfix) with ESMTP id 96F88F218F; Mon, 14 Oct 2013 11:53:42 -0400 (EDT)
Received: from NJFPSRVEXG8.research.att.com ([fe80::cdea:b3f6:3efa:1841]) by njfpsrvexg8.research.att.com ([fe80::a44a:8177:9a5d:ac00%15]) with mapi; Mon, 14 Oct 2013 11:53:29 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: William Cerveny <ippm@wjcerveny.com>, "ippm@ietf.org" <ippm@ietf.org>
Date: Mon, 14 Oct 2013 11:53:28 -0400
Thread-Topic: [ippm] My comments on draft-ietf-ippm-testplan-rfc2680-03
Thread-Index: Ac7I4T2RGPu4C1KcRSStVresHGheywAEbL9g
Message-ID: <2845723087023D4CB5114223779FA9C8AB1BE3EF@njfpsrvexg8.research.att.com>
References: <1381757286.8567.33770121.08E74A73@webmail.messagingengine.com>
In-Reply-To: <1381757286.8567.33770121.08E74A73@webmail.messagingengine.com>
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
Subject: Re: [ippm] My comments on draft-ietf-ippm-testplan-rfc2680-03
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Oct 2013 17:32:59 -0000

Thanks for your comments, Bill.
please see brief replies below,
Al

> -----Original Message-----
> From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of
> William Cerveny
> Sent: Monday, October 14, 2013 9:28 AM
> To: ippm@ietf.org
> Subject: [ippm] My comments on draft-ietf-ippm-testplan-rfc2680-03
> 
> [Not sure if I need to say that my comments are with my IPPM co-chair
> hat off, but if yes, I'm saying it :-) ]
> 
> Ann Cerveny and I are sending more detailed comments and suggestions
> (mostly grammatical) directly to the authors, but my most significant
> comments on the draft are:
> 
> 1) For "One-way Loss, ADK Sample Comparison", there is a sentence that
> starts, "The common parameters used for tests in this section are:", but
> no parameters follow.

The sentence will be revised to indicate that the 3rd level headings
describe specific experiments and the parameters are listed there,
so no information is missing from the test plan.

> 2) In some of the examples, "public" IP addresses are used (as far as I
> can tell). Should these addresses be published in an RFC?

We included the addresses in section 3 of http://tools.ietf.org/html/rfc6808
with no problems through to publication.

> 3) I think the paragraph beginning with "There is consensus ..." might
> need some clarification.

IOW, this is an examination of results collected according to metric
definitions in IPPM RFCs, rather than a comparison of system A vs. B.
I'll see what can be done to clarify.


> 4) I thought the formatting of the IF AND THEN statements for the text
> in section 2 was a little unusual.

The whole point is to turn attention to the improvements of the RFC text
if necessary (again, not A vs. B). We haven't found a need to clarify 
anything fundamental in either 2679 or 2680 testing.

> 5) I would clarify what "Imp" in figure 1 refers to although I figured
> out (I think) that it refers to "implementation".

Ok

> 
> Bill Cerveny
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm