Re: [ippm] Alvaro Retana's Discuss on draft-ietf-ippm-metric-registry-22: (with DISCUSS and COMMENT)

Alissa Cooper <alissa@cooperw.in> Fri, 13 December 2019 10:19 UTC

Return-Path: <alissa@cooperw.in>
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 0678A120832; Fri, 13 Dec 2019 02:19:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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=cooperw.in header.b=dSbc6mxb; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=M2ESdmYp
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 cNskVc5PkjTs; Fri, 13 Dec 2019 02:19:17 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D94212026E; Fri, 13 Dec 2019 02:19:17 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id D7B2D2268A; Fri, 13 Dec 2019 05:19:14 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Fri, 13 Dec 2019 05:19:14 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=a dZlijQpuOOpjbZrFU6giMiLYLG+xi+Kn2smVKZJmyQ=; b=dSbc6mxbVTCZjMABY hl3p9UYlvgRWj5enKCv+ODjTxzXINB/HiKYVqGtairAcjYKUy+az1mFOL3nuQ3oy G38iz5FjexkmuHRd7lde74KkfyIzWws1b3DjYvJPg8vfRZe10wBCDz4ug22zaRR/ VC4hNVWVCOD80o4pqv6qWui9KOChM1Wv5vQ6DbmmFC9JP2nq8gjCgdffFMjdrZW5 w1EFzBo3+ZAmiUFG3khZVSHGTrycbjYncRg9aYWZeSC7FZQTbomICXslCNQXcvLY hdgIP1UZfevYOMr4PzY2vrag9vLQXtP0UvoMTiExEh+OBscql7giIEX7RXcwBL+v v2ecQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=adZlijQpuOOpjbZrFU6giMiLYLG+xi+Kn2smVKZJm yQ=; b=M2ESdmYp7GZfRP4pG4SpRv35gQsTUSeEAALn139hnC9VevCHxNAOcKz3k a2KqUN0b7uqWXCqvX5b8TJsJdtmeZmVJUA4UcLbRrDkTFNQmC9LVyQwFd/jDW0/K 9Kxw2IZgqHy3Nd2mviqXi2XlvmwbaNhsrr76p20Sci6V88vLLPdqX2ccBtv6+TCe kgEVZdeEcLAAfGYEncGCoAdjXHnR96dqsca+yHkmdCAS58GphoT9dzc1/2bMD91E CSfCNDo5Z5t43ifQbLykg8u/z//tPminYrs9XjpMtrr9ArRhhEDCQ9rC7q9ZJhCd LCa1qrkkjZC3uCET7ohMezsN5zjSA==
X-ME-Sender: <xms:omXzXWFD8TxzFMboeYmgMWfTrZ-hHvrsdLn1VS4v0wrOhKcEP8nnVg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudelledgudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjfffgkfhfvffosehtqh hmtdhhtdejnecuhfhrohhmpeetlhhishhsrgcuvehoohhpvghruceorghlihhsshgrsegt ohhophgvrhifrdhinheqnecukfhppedutdekrdehuddruddtuddrleeknecurfgrrhgrmh epmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsthgv rhfuihiivgeptd
X-ME-Proxy: <xmx:omXzXUeTxCVWueOe3RhlX3Tb-3ccA1JWnN-6qdhzpZhqM7S2KezOOw> <xmx:omXzXfLYdAwlKt8OsU0zahIkHn7bNbXJqba7uS1VJLa7RtPesDWtJw> <xmx:omXzXRET-3mgvtu0OUjYVpj9GdXYD3_QTrJbuoXNAf9ZArHkIfFYKQ> <xmx:omXzXe6L9alIVHUHOA_qqQ3gM4Ltl_BWPqS52-_BaLKQRfieOrbYNQ>
Received: from alcoop-m-c46z.fios-router.home (pool-108-51-101-98.washdc.fios.verizon.net [108.51.101.98]) by mail.messagingengine.com (Postfix) with ESMTPA id 0172A3060267; Fri, 13 Dec 2019 05:19:13 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <4D7F4AD313D3FC43A053B309F97543CFA6F082BF@njmtexg5.research.att.com>
Date: Fri, 13 Dec 2019 05:19:12 -0500
Cc: Alvaro Retana <aretana.ietf@gmail.com>, IESG <iesg@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, "ippm-chairs@ietf.org" <ippm-chairs@ietf.org>, "ietf@wjcerveny.com" <ietf@wjcerveny.com>, "draft-ietf-ippm-metric-registry@ietf.org" <draft-ietf-ippm-metric-registry@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <03222E17-C863-4A9A-B246-A48077D93C56@cooperw.in>
References: <157541264931.4734.14501743204777647352.idtracker@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CFA6F05456@njmtexg5.research.att.com> <CAMMESsxeQJGwPW4TjXzQ_bzQKfAmv2taVorpJh2DE4QfRj9ZGQ@mail.gmail.com> <4D7F4AD313D3FC43A053B309F97543CFA6F05F66@njmtexg5.research.att.com> <CAMMESsxMUe6zG2svzoLmo3=z54j8nQpWypCx8xaRspb39aWWoQ@mail.gmail.com> <4D7F4AD313D3FC43A053B309F97543CFA6F0657C@njmtexg5.research.att.com> <CAMMESszoaP5ojm30ukfbKw-2-eKJmbijB5EjSLSGW15UNTsctw@mail.gmail.com> <4D7F4AD313D3FC43A053B309F97543CFA6F082BF@njmtexg5.research.att.com>
To: "MORTON, ALFRED C (AL)" <acm@research.att.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/YhtYINgRf_NkeTOCdLGY3NtRGKw>
Subject: Re: [ippm] Alvaro Retana's Discuss on draft-ietf-ippm-metric-registry-22: (with DISCUSS and 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: Fri, 13 Dec 2019 10:19:19 -0000

Hi Al,

I have a couple of comments in-line on this text:

> If an RFC-to-be includes a Performance Metric and a proposed Performance
> Metrics Registry entry, but the IANA and Performance Metric Expert review
> determines that one or more of the Section 5 criteria have not been met,

IANA has no role in evaluating the metrics against the Section 5 criteria, so I think they should be dropped from this sentence.

> then the IESG approval process MUST proceed with the proposed Performance
> Metrics Registry entry removed from the text. When the RFC-to-be authors
> are ready to show evidence of meeting the criteria in section 5, they
> SHOULD re-submit the proposed Performance Metrics Registry entry to IANA
> to be evaluated in consultation with the Performance Metric Experts for
> registration at that time.

For the last sentence I would suggest “Once evidence exists that the Performance Metric meets the criteria in section 5, the proposed Performance Metrics Registry entry SHOULD be submitted … .” The people who write the RFC need not be the same people who later submit the metric to the registry.

Thanks,
Alissa
 

> On Dec 6, 2019, at 1:53 PM, MORTON, ALFRED C (AL) <acm@research.att.com> wrote:
> 
> Hi Alvaro and Alissa, and other ADs who supported Alvaro's DISCUSS #2,
> 
> Alvaro and I have come to agreement on revised text,
> please see below.
> 
> Al
> 
>> -----Original Message-----
>> From: Alvaro Retana [mailto:aretana.ietf@gmail.com]
>> Sent: Thursday, December 5, 2019 1:00 PM
>> To: MORTON, ALFRED C (AL) <acm@research.att.com>; The IESG <iesg@ietf.org>
>> Cc: ippm@ietf.org; ippm-chairs@ietf.org; ietf@wjcerveny.com; draft-ietf-
>> ippm-metric-registry@ietf.org
>> Subject: RE: Alvaro Retana's Discuss on draft-ietf-ippm-metric-registry-
>> 22: (with DISCUSS and COMMENT)
>> 
>> On December 5, 2019 at 7:30:22 AM, MORTON, ALFRED C (AL) wrote:
>> 
>> Al:
>> 
>> Hi!
>> 
>> 
>>>> -----Original Message-----
>>>> From: Alvaro Retana [mailto:aretana.ietf@gmail.com]
>> ...
>>>> On December 4, 2019 at 1:38:07 PM, MORTON, ALFRED C (AL) wrote:
>> ...
>>>>> If an RFC-to-be includes a Performance Metric and a proposed
>> Performance
>>>>> Metrics Registry entry, but the IANA and Performance Metric Expert
>> review
>>>>> determines that one or more of the Section 5 criteria have not been
>> met,
>>>>> then the IESG approval process MUST proceed with the proposed
>> Performance
>>>>> Metrics Registry entry removed from the text. When the RFC-to-be
>> authors
>>>>> are ready to show evidence of meeting the criteria in section 5,
>> they
>>>>> SHOULD re-submit the proposed Performance Metrics Registry entry to
>> IANA
>>>>> to be evaluated in consultation with the Performance Metric Experts
>> for
>>>>> registration at that time.
>>>> 
>>>> This text basically says that if the criteria in §5 is not met, then
>>>> the specific entry must not be in the RFC. At some point in the
>>>> future (when the §5 criteria is met), publication of the entry can
>>>> proceed -- presumably in a different RFC.
>>> [acm]
>>> Yes.
>>>> 
>>>> As Alissa mentioned in her DISCUSS, the text needs to be generalized
>>>> to cover specifications from other SDOs. I'm not sure how preventing
>>>> publication would work there.
>>> [acm]
>>> It doesn't apply to other SDOs.
>>> There are process points that only apply to IETF and RFCs-to-be,
>>> such as the one we are discussing.
>>> IANA can receive a request from other SDOs directly, and
>>> we cover those cases separately. IWO, we do not generalize
>>> every instance of RFC to "spec", because IANA review
>>> coincides with IIESG review.
>> 
>> Your answer made go look at §8.1 again and the paragraph we're
>> discussing in context.  Just one suggestion: s/then the IESG approval
>> process MUST proceed with the proposed Performance Metrics Registry
>> entry removed from the text./then the proposed Performance Metrics
>> Registry entry MUST be removed from the text.
>> 
>> I trust that this text will make it into your next update, so I'm
>> clearing my DISCUSS.
>> 
>> Thanks!
>> 
>> Alvaro.
> [acm] 
> Thanks, I've made that change in the working text, and it will appear
> in the next version.  Thanks for clearing your DISCUSS.
> 
> Al
>