Re: [ippm] WGLC for draft-ietf-ippm-twamp-value-added-octets-01.txt

Al Morton <acmorton@att.com> Tue, 03 April 2012 15:36 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 16BD821F845F for <ippm@ietfa.amsl.com>; Tue, 3 Apr 2012 08:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.296
X-Spam-Level:
X-Spam-Status: No, score=-102.296 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, 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 gT01LQFdqrUG for <ippm@ietfa.amsl.com>; Tue, 3 Apr 2012 08:36:54 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 4578421F8582 for <ippm@ietf.org>; Tue, 3 Apr 2012 08:36:44 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id b091b7f4.0.726279.00-473.2012182.nbfkord-smmo06.seg.att.com (envelope-from <acmorton@att.com>); Tue, 03 Apr 2012 15:36:44 +0000 (UTC)
X-MXL-Hash: 4f7b190c76f1f551-737238ed5e88317f9ecfb0b5da40efa312b0b474
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 q33Fah29023789 for <ippm@ietf.org>; Tue, 3 Apr 2012 11:36:43 -0400
Received: from sflint02.pst.cso.att.com (sflint02.pst.cso.att.com [144.154.234.229]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q33Fac1Q023688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ippm@ietf.org>; Tue, 3 Apr 2012 11:36:38 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint02.pst.cso.att.com (RSA Interceptor) for <ippm@ietf.org>; Tue, 3 Apr 2012 11:36:23 -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 q33FaN7q023559 for <ippm@ietf.org>; Tue, 3 Apr 2012 11:36:23 -0400
Received: from dns.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 q33FaI4s023412 for <ippm@ietf.org>; Tue, 3 Apr 2012 11:36:18 -0400
Message-Id: <201204031536.q33FaI4s023412@alpd052.aldc.att.com>
Received: from acmt.att.com (ds135-16-251-225.dhcps.ugn.att.com[135.16.251.225](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120403153325gw1004orqee>; Tue, 3 Apr 2012 15:33:26 +0000
X-Originating-IP: [135.16.251.225]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 03 Apr 2012 11:37:26 -0400
To: Wesley Eddy <wes@mti-systems.com>, Steve Baillargeon <steve.baillargeon@ericsson.com>
From: Al Morton <acmorton@att.com>
In-Reply-To: <4F7B1114.6080603@mti-systems.com>
References: <4F742D2D.4060408@uijterwaal.nl> <4F74397D.4050902@uijterwaal.nl> <201204021408.q32E8YEo001358@alpd052.aldc.att.com> <4383945B8C24AA4FBC33555BB7B829EF178ACB2AD5@EUSAACMS0701.eamcs.ericsson.se> <4F7B1114.6080603@mti-systems.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
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=b3MHB_GQ4iAA:10 a=ofMgfj31e3cA:10 a=BLceEmwcHo]
X-AnalysisOut: [wA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a=72]
X-AnalysisOut: [wRlKAZfrG-vk3xMisA:9 a=gwvkBpJizD_J-EtwrxcA:7 a=CjuIK1q_8u]
X-AnalysisOut: [gA:10 a=bRLDSXzgruogFMFv:21 a=PfLzAtYmP6lD2Bz8:21]
Cc: IETF IPPM WG <ippm@ietf.org>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-twamp-value-added-octets-01.txt
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: Tue, 03 Apr 2012 15:36:55 -0000

I agree that the title change helps to clarify the situation,
but I also accept Steve's offer to remove the non-Ericsson
idea from the text, specifically the "Padding Length" feature.
(The single sentence or Appendix within the document would contradict
the title, and again cause confusion.)

regards,
Al


At 11:02 AM 4/3/2012, Wesley Eddy wrote:
>On 4/2/2012 12:04 PM, Steve Baillargeon wrote:
> > Hi
> >
> >>>> The authors published -value-added-octets with a WG document 
> filename(which confuses things, it has not represented WG consensus 
> at   any stage)
> >
> > My take on it is that it is OK for an Informational RFC: a subset 
> did the work, the entire WG was asked to review the write-up.
> >
>
>
>In similar cases, the document title (not to be confused with
>the filename) has clearly specified whose work it reflects.
>For instance, the document title is currently:
>"TWAMP Value-Added Octets"
>it could be something like:
>"Ericsson's TWAMP Value-Added Octets"
>
>I think that would be more clear for the record, rather than
>messing with the filename, which disappears from view once it's
>published as an RFC.
>
>
> >>>> The authors modified the draft to adopt the function of 
> asymmetrical packet size test capability and possibly other 
> functions identified in the problem statement draft.
> >
> > The only field we added in 03 is Desired Reverse Padding Length. 
> We showed a prototype @ IETF-80, people came up with suggestions, 
> we showed that our prototype could be extended.
> >
> >>>> The authors now claim to have simplified their protocol, after 
> discounting the WG's comments on the complexity of their approach 
> for about a year.
> >
> > The only field we removed in 03 is the Sender Discriminator since 
> it is not specifically related to capacity measurements. Sender 
> Discriminator looked like a good idea at the time @ IETF80 but then 
> wasn't used during our demo and is now dropped.
>
>
>To address the comments about confusion as to which parts
>reflect the pre-WG activity, and which parts have been
>incorporated after IPPM WG feedback, it might make sense
>to just have a small bit of text in section 1 to say that
>it started as an Ericsson project, but currently incorporates
>some feedback from the IPPM working group.  This would, I
>think, enhance the paragraph currently right before Section 1.1.
>
>You might list the things that reflect that feedback (e.g. the
>desired reverse padding length and removal of sender
>discriminator) an an appendix or something, if you want to be
>ultra-clear.
>
>--
>Wes Eddy
>MTI Systems