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

Henk Uijterwaal <henk@uijterwaal.nl> Mon, 02 April 2012 13:53 UTC

Return-Path: <henk@uijterwaal.nl>
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 AD40221F8567 for <ippm@ietfa.amsl.com>; Mon, 2 Apr 2012 06:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level:
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 4aai5uXYJxiG for <ippm@ietfa.amsl.com>; Mon, 2 Apr 2012 06:53:09 -0700 (PDT)
Received: from smtp-vbr13.xs4all.nl (smtp-vbr13.xs4all.nl [194.109.24.33]) by ietfa.amsl.com (Postfix) with ESMTP id C436521F854D for <ippm@ietf.org>; Mon, 2 Apr 2012 06:53:08 -0700 (PDT)
Received: from geir.local (thuis.uijterwaal.nl [82.95.178.49]) (authenticated bits=0) by smtp-vbr13.xs4all.nl (8.13.8/8.13.8) with ESMTP id q32DqVdf049185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Apr 2012 15:52:36 +0200 (CEST) (envelope-from henk@uijterwaal.nl)
Message-ID: <4F79AF1F.6030705@uijterwaal.nl>
Date: Mon, 02 Apr 2012 15:52:31 +0200
From: Henk Uijterwaal <henk@uijterwaal.nl>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Yaakov Stein <yaakov_s@rad.com>
References: <4F742D2D.4060408@uijterwaal.nl> <4F74397D.4050902@uijterwaal.nl> <07F7D7DED63154409F13298786A2ADC90433200E@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC90433200E@EXRAD5.ad.rad.co.il>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by XS4ALL Virus Scanner
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: Mon, 02 Apr 2012 13:53:09 -0000

Yaakov, others,

> I object to progressing the draft in question at the present time,
> for at least 4 reasons.
> 
> 1) The new version clearly states :
>    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.
>    ...
>    This memo describes the protocol used in the current working
>    prototype implementation of the Value-added octets feature in the
>    Ericsson lab. The prototype has been tested in real network
>    environments. The conclusion from these tests is that the Value-added
>    octets feature is able to enable estimation of metrics such as
>    available path capacity in both the forward and reverse direction of
>    the network path.
> 
> This is the definition of an individual submission track document,
> not a document to be submitted to the IESG as a product of the IPPM WG.

I understand the problem.  The reason I asked for this to make
it a WG document is that I think the WG should review this document.  The
document describes a problem plus a prototype implementation of a solution.
I think it is good to have a good description of the prototype, that has
been reviewed by the entire WG for clarity/completeness/etc of the prototype,
even if the problem we ultimately have to solve is different or we may
decide on a completely different approach towards solving the problem.

So, what I hope the first paragraph ("This memo is ... metrics") says is
"somebody in the WG did an experiment, the WG saw that it solved something
close to an existing problem, the write-up of the experiment is clear").
If it doesn't then I've done something wrong :-)

> Furthermore, the document seems to be a candidate for an "experimental" RFC, 
> not an "informational" one.

I think I agree with Steve that "informational" is the best fit, but reading
 http://www.ietf.org/u/ietfchair/info-exp.html suggests that "experimental"
might be a good choice either.  I don't think this matters too much at this
stage of the discussion though.

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)