Re: [ippm] Alvaro Retana's No Objection on draft-ietf-ippm-initial-registry-14: (with COMMENT)

"MORTON, ALFRED C (AL)" <acm@research.att.com> Wed, 04 December 2019 16:09 UTC

Return-Path: <acm@research.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 86DBA120025; Wed, 4 Dec 2019 08:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lVOZNvAJ_bBj; Wed, 4 Dec 2019 08:09:12 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CF30120019; Wed, 4 Dec 2019 08:09:12 -0800 (PST)
Received: from pps.filterd (m0049459.ppops.net [127.0.0.1]) by m0049459.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id xB4G77Hr004404; Wed, 4 Dec 2019 11:09:11 -0500
Received: from tlpd255.enaf.dadc.sbc.com (sbcsmtp3.sbc.com [144.160.112.28]) by m0049459.ppops.net-00191d01. with ESMTP id 2wpe7r3ask-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 04 Dec 2019 11:09:10 -0500
Received: from enaf.dadc.sbc.com (localhost [127.0.0.1]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id xB4G98Ni022431; Wed, 4 Dec 2019 10:09:10 -0600
Received: from zlp30494.vci.att.com (zlp30494.vci.att.com [135.46.181.159]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id xB4G94gP022262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Dec 2019 10:09:04 -0600
Received: from zlp30494.vci.att.com (zlp30494.vci.att.com [127.0.0.1]) by zlp30494.vci.att.com (Service) with ESMTP id 01B414009E76; Wed, 4 Dec 2019 16:09:04 +0000 (GMT)
Received: from clpi183.sldc.sbc.com (unknown [135.41.1.46]) by zlp30494.vci.att.com (Service) with ESMTP id D60DC4009E72; Wed, 4 Dec 2019 16:09:03 +0000 (GMT)
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id xB4G93wb032177; Wed, 4 Dec 2019 10:09:03 -0600
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.255.15]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id xB4G8rDF031310; Wed, 4 Dec 2019 10:08:53 -0600
Received: from exchange.research.att.com (njbdcas1.research.att.com [135.197.255.61]) by mail-green.research.att.com (Postfix) with ESMTP id 33CF1E367D; Wed, 4 Dec 2019 11:04:58 -0500 (EST)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njbdcas1.research.att.com ([fe80::8c6b:4b77:618f:9a01%11]) with mapi id 14.03.0468.000; Wed, 4 Dec 2019 11:08:52 -0500
From: "MORTON, ALFRED C (AL)" <acm@research.att.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-ippm-initial-registry@ietf.org" <draft-ietf-ippm-initial-registry@ietf.org>, Brian Trammell <ietf@trammell.ch>, "ippm-chairs@ietf.org" <ippm-chairs@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: Alvaro Retana's No Objection on draft-ietf-ippm-initial-registry-14: (with COMMENT)
Thread-Index: AQHVqinLD0E3R55SSEWFwzkXg2FrvaeqHrxg
Date: Wed, 04 Dec 2019 16:08:52 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CFA6F0590A@njmtexg5.research.att.com>
References: <157541243765.4760.10404134824479029590.idtracker@ietfa.amsl.com>
In-Reply-To: <157541243765.4760.10404134824479029590.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [156.106.224.110]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-04_03:2019-12-04,2019-12-04 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 lowpriorityscore=0 mlxlogscore=999 clxscore=1015 bulkscore=0 priorityscore=1501 mlxscore=0 malwarescore=0 adultscore=0 spamscore=0 impostorscore=0 phishscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912040134
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/pwMQAKi5tpgdDzLQ68ozPwjvdy4>
Subject: Re: [ippm] Alvaro Retana's No Objection on draft-ietf-ippm-initial-registry-14: (with COMMENT)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 04 Dec 2019 16:09:15 -0000

Hi Alvaro,

Thanks again for your review and comments.

Please see replies marked [acm] below.
Al

> -----Original Message-----
> From: Alvaro Retana via Datatracker [mailto:noreply@ietf.org]
> Sent: Tuesday, December 3, 2019 5:34 PM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-ippm-initial-registry@ietf.org; Brian Trammell
> <ietf@trammell.ch>; ippm-chairs@ietf.org; ippm@ietf.org
> Subject: Alvaro Retana's No Objection on draft-ietf-ippm-initial-registry-
> 14: (with COMMENT)
> 
> Alvaro Retana has entered the following ballot position for
> draft-ietf-ippm-initial-registry-14: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_iesg_statement_discuss-2Dcriteria.html&d=DwIDaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=ILN34KWl728d4MwapM6b2uFD-
> AN_qvG3pywSVlI__xI&s=nSlIN1hkc12vDUVhxTXZ0oJvW7f6yWlIlilAarPCnE4&e=
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__datatracker.ietf.org_doc_draft-2Dietf-2Dippm-2Dinitial-
> 2Dregistry_&d=DwIDaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=ILN34KWl728d4MwapM6b2uFD-
> AN_qvG3pywSVlI__xI&s=J65nyx-0afWUBtjfKbF2_j7nKQmwb87O9qpiPkDnXkE&e=
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I have a significant issue related to the approval of this initial
> registry,
> and then a minor point.
> 
> (1) This is the significant issue:
> 
> §2:
> 
>    This document defines the initial set of Performance Metrics Registry
>    entries, for which IETF approval (following development in the IP
>    Performance Metrics (IPPM) Working Group) will satisfy the
>    requirement for Expert Review.  Most are Active Performance Metrics,
>    which are based on RFCs prepared in the IPPM working group of the
>    IETF, according to their framework [RFC2330] and its updates.
> 
> s/IETF approval/IESG Approval
> There is no "IETF approval" policy in rfc8126.
> 
> Even though it is self-serving for this document to provide guidance on the
> approval for the new registry entries, I think that it should be possible to do
> so using IESG Approval given that these initial entries into the new registry
> have been reviewed by the WG.  However, draft-ietf-ippm-metric-registry only
> explicitly talks about using Specification Required (including Expert Review),
> and it makes no exceptions.
> 
> This document should not make statements about criteria used for this initial
> registration, so §2 should be deleted.
[acm] 
OK, but I think it is fair to keep parts of Section 2, which is the Scope.

Here's the revised version I suggest:
This document defines a set of initial Performance Metrics Registry entries. 
Most are Active Performance Metrics, which are based on RFCs prepared in the 
IPPM working group of the IETF, according to their framework [RFC2330] and its
updates.

> 
> draft-ietf-ippm-metric-registry should be explicit about the initial population
> of the registry.  I am them balloting DISCUSS on that other document to address
> the approval of the initial registry entries in this document.
[acm] 
Added an explicit mention of the initial-registry draft at the end of the Scope
of draft-ietf-ippm-metric-registry.


> 
> (2) Minor point:
> 
> §1: "The process in [I-D.ietf-ippm-metric-registry] also requires that new
> entries are administered by IANA through Expert Review or IETF Standards
> action, which will ensure that the metrics are tightly defined."   The
> registration policy defined in I-D.ietf-ippm-metric-registry is "Specification
> Required", which requires the review of an expert.
> 
[acm] 
good catch, fixed.