Re: [ippm] Alvaro Retana's No Objection on draft-ietf-ippm-initial-registry-14: (with COMMENT)
Alvaro Retana <aretana.ietf@gmail.com> Wed, 04 December 2019 16:31 UTC
Return-Path: <aretana.ietf@gmail.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 1F581120073; Wed, 4 Dec 2019 08:31:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Zf4MHooWu_En; Wed, 4 Dec 2019 08:31:21 -0800 (PST)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B8AD12002E; Wed, 4 Dec 2019 08:31:21 -0800 (PST)
Received: by mail-wr1-x42a.google.com with SMTP id z7so9298807wrl.13; Wed, 04 Dec 2019 08:31:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=J++5mb4u92OnQ3ZOut8uafH4Lxzpkg0aSQtSWl60CBc=; b=PLPxYT78X7GZgtVPtOJ1OQnhTD0WQSs52tm1LTZi++YZ37ThvB2ceL9MQqHNyvoCy8 DedNmuTCaEvqmbI/9mjpK0J/+uNmtEHOHprpWsZyIOrz/oaoQgSN4BYoxmOORKQ3RJ+J HpDUQss0i9ZVXn2jXilGjdRMKiK9THFJJEyvgylXf/2uTZAe/AqWqMvuaZXFobNLGHMO ZFl1AKjgBcytsW1oYyZ8lIIyQ+H6KH3LcdUWIfVfJEdu345bOQ64YgvWRUmX6e2ADGMe HmXAfV06pCucNHZ6geiPuni97bER4Pl/Km0m3whLlzIggnsdWdEirMjNNRl0GT4PtcVI C+3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=J++5mb4u92OnQ3ZOut8uafH4Lxzpkg0aSQtSWl60CBc=; b=bOznRR9+eV+AipJNAc02hOnh295AypWeNjBagwiA9RLJ4F7DmMHJ3KvCvWgHfRCUr1 eGEJ2muMzOMPTdFm2P7Gahd5p4U1vrDnWPmXIdJCh6hT/TCZ0QRIH9I88l6ccSw0YquM 9ep0iXSOnpGmDADHocwRL4qxot5ZuU6f+PH1dxD59Mw8C3O/id+mSjR6TST6mGxLjCaq kG/V69wd+ugAtYttbja6vC2II5B9fGReLJtifOirmkRs+DUam4bubgDPgeJm1KXOrTYs Eybdq4n4n6v17RQbokpaFUvkt0IPNmcxa28fvD2dMtV1lJmCVlhfm/HBV7WZph4C5JA+ ykhw==
X-Gm-Message-State: APjAAAULH97X+Ut0m64XWp3b9YDU9hlVRVFZzWiHh/JGjSjdz5/EKS9Z +OZyMGRiy3aiS8iOSk4rOzZbVUbhQZR69oaWmAE=
X-Google-Smtp-Source: APXvYqzDEFeTQyDbfXj8DsqjSf3BF9lQr0SFhPx59A9lAbscLxNp5zXhX6Ur2v/kPtpPWW22FmdoXuumV56vZYqXY2A=
X-Received: by 2002:adf:cd92:: with SMTP id q18mr4930505wrj.261.1575477079715; Wed, 04 Dec 2019 08:31:19 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 4 Dec 2019 08:31:19 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <4D7F4AD313D3FC43A053B309F97543CFA6F0590A@njmtexg5.research.att.com>
References: <157541243765.4760.10404134824479029590.idtracker@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CFA6F0590A@njmtexg5.research.att.com>
MIME-Version: 1.0
Date: Wed, 04 Dec 2019 08:31:19 -0800
Message-ID: <CAMMESsw0j8-pO8xW5_2O2XNhyhx8wHYD+q6SyJFLoWr+a7Zc_Q@mail.gmail.com>
To: "MORTON, ALFRED C (AL)" <acm@research.att.com>, The IESG <iesg@ietf.org>
Cc: "ippm@ietf.org" <ippm@ietf.org>, "ippm-chairs@ietf.org" <ippm-chairs@ietf.org>, "draft-ietf-ippm-initial-registry@ietf.org" <draft-ietf-ippm-initial-registry@ietf.org>, Brian Trammell <ietf@trammell.ch>
Content-Type: multipart/alternative; boundary="000000000000b034c90598e357d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/0nV5O8v4WgrowCZyReqh9B_bsYg>
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:31:23 -0000
Thanks Al, the changes below los good to me. Alvaro. On December 4, 2019 at 11:09:11 AM, MORTON, ALFRED C (AL) ( acm@research.att.com) wrote: 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.
- [ippm] Alvaro Retana's No Objection on draft-ietf… Alvaro Retana via Datatracker
- Re: [ippm] Alvaro Retana's No Objection on draft-… MORTON, ALFRED C (AL)
- Re: [ippm] Alvaro Retana's No Objection on draft-… Alvaro Retana