Re: [ippm] I-D Action: draft-ietf-ippm-metric-registry-18 and -initial-registry-10

"MORTON, ALFRED C (AL)" <acm@research.att.com> Tue, 19 March 2019 14:44 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 3A3CA131350 for <ippm@ietfa.amsl.com>; Tue, 19 Mar 2019 07:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=0.85, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 QPq7XAEb4w9p for <ippm@ietfa.amsl.com>; Tue, 19 Mar 2019 07:44:11 -0700 (PDT)
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 9514E13130C for <ippm@ietf.org>; Tue, 19 Mar 2019 07:44:11 -0700 (PDT)
Received: from pps.filterd (m0049458.ppops.net [127.0.0.1]) by m0049458.ppops.net-00191d01. (8.16.0.27/8.16.0.27) with SMTP id x2JEbkl8018415; Tue, 19 Mar 2019 10:43:50 -0400
Received: from tlpd255.enaf.dadc.sbc.com (sbcsmtp3.sbc.com [144.160.112.28]) by m0049458.ppops.net-00191d01. with ESMTP id 2raywwv98n-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 19 Mar 2019 10:43:49 -0400
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 x2JEhl9b050635; Tue, 19 Mar 2019 09:43:49 -0500
Received: from zlp30497.vci.att.com (zlp30497.vci.att.com [135.46.181.156]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id x2JEhfKM050320; Tue, 19 Mar 2019 09:43:41 -0500
Received: from zlp30497.vci.att.com (zlp30497.vci.att.com [127.0.0.1]) by zlp30497.vci.att.com (Service) with ESMTP id 8D9144000694; Tue, 19 Mar 2019 14:43:41 +0000 (GMT)
Received: from clpi183.sldc.sbc.com (unknown [135.41.1.46]) by zlp30497.vci.att.com (Service) with ESMTP id 624374000696; Tue, 19 Mar 2019 14:43:41 +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 x2JEhfZW020651; Tue, 19 Mar 2019 09:43:41 -0500
Received: from mail-azure.research.att.com (mail-azure.research.att.com [135.207.255.18]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id x2JEhYCT019957; Tue, 19 Mar 2019 09:43:34 -0500
Received: from exchange.research.att.com (njbdcas1.research.att.com [135.197.255.61]) by mail-azure.research.att.com (Postfix) with ESMTP id 56985E0A3A; Tue, 19 Mar 2019 10:43:33 -0400 (EDT)
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.0439.000; Tue, 19 Mar 2019 10:43:01 -0400
From: "MORTON, ALFRED C (AL)" <acm@research.att.com>
To: "ippm@ietf.org" <ippm@ietf.org>, Michelle Cotton <michelle.cotton@iana.org>
Thread-Topic: [ippm] I-D Action: draft-ietf-ippm-metric-registry-18 and -initial-registry-10
Thread-Index: AdTeXtjZAxjGk5DERVudUaXBk29bEw==
Date: Tue, 19 Mar 2019 14:43:12 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF6C00645C@njmtexg5.research.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [69.141.203.172]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-19_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903190108
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/RQ0_Gf1Hh9JV61_NHQWNL3BQhP0>
Subject: Re: [ippm] I-D Action: draft-ietf-ippm-metric-registry-18 and -initial-registry-10
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: Tue, 19 Mar 2019 14:44:14 -0000

IPPM,

The WG Chairs have asked me to lead a discussion of the
two Registry Drafts during the IPPM session, and hopefully 
close the extended WGLC. URLs to the drafts are appended
to this message.

The current versions -18 and -10 address the comments on
ippm-list up to today (but see below).

At my request, Michelle Cotton of IANA provided 
yet-another-early-IANA-review, and her comments on the 
-registry-17 draft have been resolved in -18 as well.
*Thanks Michelle!*

AFAIK*, The remaining issue is whether we retain or 
remove the proposed URN namespaces for metric names.
I asked the following question on the list several weeks
back:
> [acm]
> If we have a unique numerical ID for each registered metric, paired
> with a unique Name determined according to a carefully constructed format
> with some extensibility:
> https://tools.ietf.org/html/draft-ietf-ippm-metric-registry-17#section-
> 7.1.2
> 
> what additional benefits do we gain when we create a new URN by appending
> the Name to   urn:ietf:<metrics or param or ??> ?
> 
> There seems to be some overlap between a unique name in the Performance
> Metrics Registry and a URN for the same Registered Metric,
> and I think we should weigh the value of having both (or just the Name,
> in a registry).

For me, the Identifier is sufficient for use in control protocols,
and the unique Name (not URN) is sufficient to document test results.

So, if I have overlooked an issue, please let me know, 
and please come prepared to discuss these drafts.

thanks,
Al, for the many co-authors

* Some editorial issues may remain, as well. At least one of my co-authors
has offered to help find them. We know that the RFC Editor will do a 
more complete review than we can ever conjure-up, eventually.

> -----Original Message-----
> From: ippm [mailto:ippm-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: Monday, March 11, 2019 5:43 PM
> To: i-d-announce@ietf.org
> Cc: ippm@ietf.org
> Subject: [ippm] I-D Action: draft-ietf-ippm-metric-registry-18.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the IP Performance Measurement WG of the
> IETF.
> 
>         Title           : Registry for Performance Metrics
>         Authors         : Marcelo Bagnulo
>                           Benoit Claise
>                           Philip Eardley
>                           Al Morton
>                           Aamer Akhter
> 	Filename        : draft-ietf-ippm-metric-registry-18.txt
> 	Pages           : 34
> 	Date            : 2019-03-11
> 
> Abstract:
>    This document defines the format for the IANA Performance Metrics
>    Registry.  This document also gives a set of guidelines for
>    Registered Performance Metric requesters and reviewers.
> 
https://tools.ietf.org/html/draft-ietf-ippm-metric-registry-18

[acm] 
And
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP Performance Measurement WG of the IETF.

        Title           : Initial Performance Metrics Registry Entries
        Authors         : Al Morton
                          Marcelo Bagnulo
                          Philip Eardley
                          Kevin D'Souza
	Filename        : draft-ietf-ippm-initial-registry-10.txt
	Pages           : 79
	Date            : 2019-03-11

Abstract:
   This memo defines the set of Initial Entries for the IANA Performance
   Metrics Registry.  The set includes, UDP Round-trip Latency and Loss,
   Packet Delay Variation, DNS Response Latency and Loss, UDP Poisson
   One-way Delay and Loss, UDP Periodic One-way Delay and Loss, ICMP
   Round-trip Latency and Loss, and TCP round-trip Latency and Loss.
https://tools.ietf.org/html/draft-ietf-ippm-initial-registry-10