Re: [ippm] On draft-ietf-ippm-twamp-valua-added-octets

Steve Baillargeon <steve.baillargeon@ericsson.com> Mon, 26 March 2012 07:48 UTC

Return-Path: <steve.baillargeon@ericsson.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 7C50A21F856D for <ippm@ietfa.amsl.com>; Mon, 26 Mar 2012 00:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 8WjVb2r4xCes for <ippm@ietfa.amsl.com>; Mon, 26 Mar 2012 00:48:54 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 815FB21F857A for <ippm@ietf.org>; Mon, 26 Mar 2012 00:48:54 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q2Q7mrWR009428 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 26 Mar 2012 02:48:54 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.55]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Mon, 26 Mar 2012 03:48:52 -0400
From: Steve Baillargeon <steve.baillargeon@ericsson.com>
To: Henk Uijterwaal <henk@uijterwaal.nl>
Date: Mon, 26 Mar 2012 03:48:50 -0400
Thread-Topic: [ippm] On draft-ietf-ippm-twamp-valua-added-octets
Thread-Index: Ac0Fq0PcI74+OHQ+RUWN1Dya8OyyQAFdomDQ
Message-ID: <4383945B8C24AA4FBC33555BB7B829EF178A8FD467@EUSAACMS0701.eamcs.ericsson.se>
References: <4F1E8DF2.2050401@uijterwaal.nl> <4F338A6F.4070706@uijterwaal.nl> <4F4C9C19.6060609@uijterwaal.nl> <4F66EFAE.8040501@uijterwaal.nl>
In-Reply-To: <4F66EFAE.8040501@uijterwaal.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/mixed; boundary="_002_4383945B8C24AA4FBC33555BB7B829EF178A8FD467EUSAACMS0701e_"
MIME-Version: 1.0
Cc: IETF IPPM WG <ippm@ietf.org>
Subject: Re: [ippm] On draft-ietf-ippm-twamp-valua-added-octets
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: Mon, 26 Mar 2012 07:48:55 -0000

Good morning Henk
We have updated the draft as requested.

See enclosed notice.

Please let us know if the changes are OK.

Regards
Steve


-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of Henk Uijterwaal
Sent: March-19-12 9:35 AM
To: IETF IPPM WG
Subject: [ippm] On draft-ietf-ippm-twamp-valua-added-octets

On 28/02/2012 10:19, Henk Uijterwaal wrote:
> Please see below.  This document has meanwhile been submitted as 
> draft-ietf-ippm-twamp-valua-added-octets and the authors have asked 
> for comments.

Speaking as both myself and a WG chair, not sure where to draw the line.

I have reviewed the document.  Technically, it looks quite clear, I have some comments on how to fit this into the bigger picture though:

1. The reason for publishing this draft is to document the work done by the
   authors in a permanent way.  The WG has reviewed the document to verify
   that the description of the work done is clear.

   The document is not published as "the WG consensus solution" to a
   specific problem, as there is no consensus amongst the WG on what
   the problem is.  There has been no discussion and there no
   consensus either if this solution is the one the WG prefers.

   The abstract and introduction should explicitly says this.

   What I want to avoid, is that this gets to be the
   de facto standard without WG consensus on the problem or the solution.

2. The IANA section can be dropped.  Yes, there is a registry and the
   authors made private extension to it, but now that the experiment is
   over, they can be removed again, and IANA doesn't have to do anything
   now.

3. I think it would be good to mention that there is a working prototype
   implementation of these extensions, with a reference if that is at all
   possible.  The document should say that it describes the prototype as
   it was on the day the document was written.

   I did noticed changes in the protocol extensions over the versions.
   Is this because the prototype was modified?

Henk



--
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
                                          http://www.uijterwaal.nl
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project) _______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm
--- Begin Message ---
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Performance Metrics Working Group of the IETF.

        Title           : TWAMP Value-Added Octets
        Author(s)       : Steve Baillargeon
                          Christofer Flinta
                          Andreas Johnsson
                          Svante Ekelin
        Filename        : draft-ietf-ippm-twamp-value-added-octets-01.txt
        Pages           : 16
        Date            : 2012-03-26

   This memo describes an extension to the TWAMP test protocol for
   identifying and managing packet trains, which enables measuring
   capacity metrics like the available path capacity, tight section
   capacity and UDP delivery rate in the forward and reverse path
   directions.

   This memo is the product of a working prototype. It does not
   represent a consensus of the IETF community. The IETF community is
   currently working on the problem statement and has not reached
   consensus on the preferred method for measuring capacity metrics.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ippm-twamp-value-added-octets-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ippm-twamp-value-added-octets-01.txt

_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm
--- End Message ---