Re: [ippm] AD review of draft-ietf-ippm-reporting-metrics-07

Al Morton <acmorton@att.com> Fri, 09 March 2012 13:46 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 12A7921F865C for <ippm@ietfa.amsl.com>; Fri, 9 Mar 2012 05:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.441
X-Spam-Level:
X-Spam-Status: No, score=-105.441 tagged_above=-999 required=5 tests=[AWL=0.355, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, 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 XFUjA1W5Wo7z for <ippm@ietfa.amsl.com>; Fri, 9 Mar 2012 05:46:45 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id 5283B21F8658 for <ippm@ietf.org>; Fri, 9 Mar 2012 05:46:45 -0800 (PST)
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-8.tower-119.messagelabs.com!1331300803!18400094!1
X-Originating-IP: [144.160.20.145]
X-StarScan-Version: 6.5.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22298 invoked from network); 9 Mar 2012 13:46:44 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-8.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Mar 2012 13:46:44 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q29DlEM7021951 for <ippm@ietf.org>; Fri, 9 Mar 2012 08:47:14 -0500
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q29DlCiO021898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ippm@ietf.org>; Fri, 9 Mar 2012 08:47:12 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor) for <ippm@ietf.org>; Fri, 9 Mar 2012 08:46:24 -0500
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 q29DkNdJ010845 for <ippm@ietf.org>; Fri, 9 Mar 2012 08:46:23 -0500
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q29DkC52010261 for <ippm@ietf.org>; Fri, 9 Mar 2012 08:46:16 -0500
Message-Id: <201203091346.q29DkC52010261@alpd052.aldc.att.com>
Received: from acmt.att.com (vpn-135-70-13-56.vpn.west.att.com[135.70.13.56](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120309134339gw1004or9ue>; Fri, 9 Mar 2012 13:43:40 +0000
X-Originating-IP: [135.70.13.56]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 09 Mar 2012 08:47:15 -0500
To: Wesley Eddy <weddy@hyperelliptic.com>, draft-ietf-ippm-reporting-metrics@tools.ietf.org
From: Al Morton <acmorton@att.com>
In-Reply-To: <4F59970A.6090207@hyperelliptic.com>
References: <4F59970A.6090207@hyperelliptic.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
Cc: ippm@ietf.org
Subject: Re: [ippm] AD review of draft-ietf-ippm-reporting-metrics-07
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: Fri, 09 Mar 2012 13:46:46 -0000

Thanks for your careful review and comments, Wes.
These are all good clarifications.

We'll address them ASAP, but possibly after the document submission
deadline on Monday, sorry in advance if it works out that way...

At 12:37 AM 3/9/2012, Wesley Eddy wrote:
>Hi, I've reviewed the reporting metrics document submitted
>for publication and have a few comments on it that should
>be looked at:
>
>1 - in section 2, paragraph 4, the first bullet; it would
>     make later text more clear if this explicitly said that
>     it's the "restricted" version, and I also think we mean
>     to say congestion control rather than flow control, to
>     be more precise.  I would suggest:
>     "[RFC3148] includes restrictions of congestion control
>      and the notion of unique bits delivered"
>
>2 - In figure 1 and 2, I think t_i and q_i should be grouped
>     with parenthesis for clarity, since they should be added
>     together within the summation
>
>3 - I think the notation on the summation in figure 2 could
>     use some help.  I think it would be more clear with an
>     "i=j" on the bottom and "j+(L-1)" on the top, with text
>     saying "where j is the hop number where the loop begins"
>
>4 - I think it should be specifically stated that "TTL" is
>     the packet's initial TTL at the source, in Figure 2.
>
>5 - I think in section 4.3 that it should be acknowledged that
>     the link-layer can (and does) discard frames, resulting in
>     loss at the IP-layer.  Since link-layer checksums often
>     cover more than just headers (like IP's does), errors in
>     transmission may more frequently generate lost packets
>     than errored packets that arrive at the destination.
>
>Other than that, I think this is a pretty good document and is
>ready to go.
>
>--
>Wes Eddy
>MTI Systems