Re: [CCAMP] Fwd: Re: Fwd: Re: WG Last Call: draft-ietf-ccamp-dpm

Lou Berger <lberger@labn.net> Wed, 06 June 2012 19:27 UTC

Return-Path: <lberger@labn.net>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F3A521F85D1 for <ccamp@ietfa.amsl.com>; Wed, 6 Jun 2012 12:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.678
X-Spam-Level:
X-Spam-Status: No, score=-99.678 tagged_above=-999 required=5 tests=[AWL=0.483, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.1, 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 qgyHl1MfhyTB for <ccamp@ietfa.amsl.com>; Wed, 6 Jun 2012 12:27:23 -0700 (PDT)
Received: from oproxy1-pub.bluehost.com (oproxy1.bluehost.com [IPv6:2605:dc00:100:2::a1]) by ietfa.amsl.com (Postfix) with SMTP id 6772A21F85CC for <ccamp@ietf.org>; Wed, 6 Jun 2012 12:27:23 -0700 (PDT)
Received: (qmail 11364 invoked by uid 0); 6 Jun 2012 19:27:22 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy1.bluehost.com with SMTP; 6 Jun 2012 19:27:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=gF74Vvvck7Cg9bsrjglEt0FE1I0tcDCbMBXDX1UZJY8=; b=ZH479t5p3Y6DBXKEV9HsSU5rMeyNZNQY7dPMRYf7+HW5ozJOL19qXyhoyImtLq7XK6N2O2h75b8U1rKOC8wS6Ddm6Trg+YAVXHMfQc6znflKF2ARsx1vKR/JbQkrSJAs;
Received: from box313.bluehost.com ([69.89.31.113]:55570 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1ScLt4-0007Uh-CA; Wed, 06 Jun 2012 13:27:22 -0600
Message-ID: <4FCFAF16.3090406@labn.net>
Date: Wed, 06 Jun 2012 15:27:18 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Al Morton <acmorton@att.com>
References: <201205201341.q4KDfgjJ014852@alpd052.aldc.att.com>
In-Reply-To: <201205201341.q4KDfgjJ014852@alpd052.aldc.att.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: ccamp@ietf.org, dbrungard@att.com
Subject: Re: [CCAMP] Fwd: Re: Fwd: Re: WG Last Call: draft-ietf-ccamp-dpm
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 19:27:24 -0000

Al,

I take it that the review by the Performance Metrics Directorate is now
complete.  Is this correct?

Thanks again for your review.

Lou

On 5/20/2012 9:42 AM, Al Morton wrote:
> Lou and Deborah,
> 
> As requested, my brief review of the dpm draft is below.
> I've also asked for a Performance Metrics Directorate volunteer
> who could review the draft quickly. If another review is coming,
> I'll let you know.
> 
> Al
> 
> 
>> Date: Sat, 19 May 2012 10:06:22 -0400
>> To: Lou Berger <lberger@labn.net>
>> From: Al Morton <acmorton@att.com>
>> Subject: Re: Fwd: Re: [CCAMP] WG Last Call: draft-ietf-ccamp-dpm
>> Cc: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
>>
>> Hi Lou,
>>
>> I took a quick look this morning, the authors have nicely adopted
>> the familiar metric framework used in other performance work,
>> and I like the metric naming - very straightforward to sort out
>> the names once you read the explanation in section 3,
>> although they could say explicitly how they've done it, so it lends
>> to extension in the future.
>>
>> I would suggest they give the acronym expansion in each section.
>> for example:
>>
>>
>>> 5.2.  Metric Name
>>>
>>>    RRFD  =  RESV Received, Forward Datapath
>>
>>
>> One word choice in section 1 could be improved:
>>
>>
>>>
>>>    This document defines a series of performance metrics to evaluate the
>>>    availability of data path during the signaling process.
>>
>> I would suggests/availability/connectivity/
>>
>> "availability" has many more rigorous definitions than the
>> test pattern used here.
>>
>> A minor concern:
>> It seems that the length of the test signal will influence
>> the delay measurement, the simple serialization time for bits
>> in the first packet of the signal, which it seems could be a
>> Jumbo packet. This should be mentioned as it is applicable as
>> a potential source of error for all the metrics. I realize this may
>> be negligible on high speed interfaces using a single packet for
>> the test signal - but they've left the option for long test
>> signals. There is clear motivation to use small packets from a
>> performance-bias perspective.
>>
>> -=-=-=-=-=-=-
>>
>> In recent news, the Performance Metrics Directorate has been formed
>> in the OPS area, and we review drafts when WG chairs request.
>> As PMDir Admin, I'd be glad to ask for a review volunteer.
>> Let me know.
>>
>> We usually try to do early review of WG doc candidates rather
>> than WG Last Call, simply because the feedback might be extensive.
>> http://www.ietf.org/iesg/directorate/performance-metrics.html
>>
>> hope this helps,
>> Al
> 
> 
> 
> 
>