Re: [ippm] WG Last Call: draft-ietf-ippm-initial-registry & draft-ietf-ippm-metric-registry
worley@ariadne.com (Dale R. Worley) Mon, 18 February 2019 23:01 UTC
Return-Path: <worley@alum.mit.edu>
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 69DDD1310AF for <ippm@ietfa.amsl.com>; Mon, 18 Feb 2019 15:01:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level:
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 TGRDa0bHrYef for <ippm@ietfa.amsl.com>; Mon, 18 Feb 2019 15:01:08 -0800 (PST)
Received: from resqmta-po-08v.sys.comcast.net (resqmta-po-08v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:167]) (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 E36BF1310B0 for <ippm@ietf.org>; Mon, 18 Feb 2019 15:01:05 -0800 (PST)
Received: from resomta-po-13v.sys.comcast.net ([96.114.154.237]) by resqmta-po-08v.sys.comcast.net with ESMTP id vpTjgKGy3aNycvruLghuQB; Mon, 18 Feb 2019 23:01:05 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1550530865; bh=e6Jt7Eqs/w7stXRRjkB4IJDr9iO2mzVaP3imG84iSEg=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=iE7SBVTIjj7UMjHEhRO+xk502Dx2NOlqFexDjCESktKTIi8mPVR7Esfer/QfKboqj J+1EOIad3MY+8FYIku1f7anR2cKH9joMHVG4WUxTXH5x1M2TsHmKwMR2hR5jKW849G afNIwQBZet43RfbJwovMmKmkx7p6Q7EuVsJYFxMh3PJqaObeeCkpDNFUYLtjAchc4d TdezEwvWYlZVIA/DB1Kc4InqV1x9zi6mpcZfWLAvFyZY0SeT22nfZc5UpAHn22REgt AgNFda6KggcHINxO00wfMeQDWH/MSAVwUCwuUV6A4vTOq8G24YLzJQ2LwqHy55mq5m DOedfy5RFx3zw==
Received: from hobgoblin.ariadne.com ([50.245.49.139]) by resomta-po-13v.sys.comcast.net with ESMTPA id vruJgHZPpPgV4vruKgSiAM; Mon, 18 Feb 2019 23:01:05 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedutddrtddvgddtgecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecunecujfgurhephffvufgjshestddttddttddttdenucfhrhhomhepfihorhhlvgihsegrrhhirggunhgvrdgtohhmucdlffgrlhgvucftrdcuhghorhhlvgihmdenucfkphephedtrddvgeehrdegledrudefleenucfrrghrrghmpehhvghlohephhhosghgohgslhhinhdrrghrihgrughnvgdrtghomhdpihhnvghtpeehtddrvdeghedrgeelrddufeelpdhmrghilhhfrhhomhepfihorhhlvgihsegrlhhumhdrmhhithdrvgguuhdprhgtphhtthhopegurhgrfhhtqdhivghtfhdqihhpphhmqdhmvghtrhhitgdqrhgvghhishhtrhihrdgrlhhlsehivghtfhdrohhrghdprhgtphhtthhopegurhgrfhhtqdhivghtfhdqihhpphhmqdhinhhithhirghlqdhrvghgihhsthhrhidrrghllhesihgvthhfrdhorhhgpdhrtghpthhtohepthhprghulhihpeegtdgrphhplhgvrdgtohhmsegumhgrrhgtrdhivghtfhdrohhrghdprhgtphhtthhopehiphhpmhesihgvthhfrdhorhhgpdhrtghpthhtoheprggtmhesrhgvshgvrghrtghhrdgrthhtrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-Xfinity-VMeta: sc=??;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id x1IN12VT025581; Mon, 18 Feb 2019 18:01:02 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id x1IN111u025546; Mon, 18 Feb 2019 18:01:01 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: acm@research.att.com, ippm@ietf.org, tpauly=40apple.com@dmarc.ietf.org, draft-ietf-ippm-initial-registry.all@ietf.org, draft-ietf-ippm-metric-registry.all@ietf.org
In-Reply-To: <051001d4c52e$c6b67200$4001a8c0@gateway.2wire.net> (ietfa@btconnect.com)
Sender: worley@ariadne.com
Date: Mon, 18 Feb 2019 18:01:01 -0500
Message-ID: <87o978ln0y.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/c-6EEUY7JU8RuR_V5aw2ziFXG4s>
Subject: Re: [ippm] WG Last Call: draft-ietf-ippm-initial-registry & draft-ietf-ippm-metric-registry
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: Mon, 18 Feb 2019 23:01:09 -0000
tom petch <ietfa@btconnect.com> writes: > I see several candidates for a Group name > Registry for Performance Metrics > Performance Metric Registry > Performance Metrics Registry > New Performance Metrics Registry > which seem to used interchangeably - perhaps not such a good idea for an > I-D. That's something to avoid -- using multiple terms to mean the same thing. That's *really easy* for people who have been working with the material three or four years to do, because they all know all the terms and never even realize that they're using various terms. But it's a serious impediment for someone who wants to learn the subject matter by reading the document, because they keep running into terms that aren't defined, and the have to guess which terms mean the same thing and which don't. Or in short, there's a *reason* that most I-Ds these days have Section 2. Terminology Checking back with the drafts, I see that draft-ietf-ippm-metric-registry-17 does have a terminology section, but draft-ietf-ippm-initial-registry-09 only has the statement "Note: Efforts to synchronize structure and terminology with [I-D.ietf-ippm-metric-registry] will likely be incomplete until both drafts are stable." You really want to get the Terminology section in order (probably having draft-ietf-ippm-initial-registry (normatively!) point to draft-ietf-ippm-metric-registry), and then ensure all of the text uses the terms defined therein. Dale
- [ippm] WG Last Call: draft-ietf-ippm-initial-regi… Tommy Pauly
- Re: [ippm] WG Last Call: draft-ietf-ippm-initial-… Tommy Pauly
- Re: [ippm] WG Last Call: draft-ietf-ippm-initial-… tom petch
- Re: [ippm] WG Last Call: draft-ietf-ippm-initial-… MORTON, ALFRED C (AL)
- Re: [ippm] WG Last Call: draft-ietf-ippm-initial-… Dale R. Worley
- Re: [ippm] WG Last Call: draft-ietf-ippm-initial-… tom petch
- Re: [ippm] WG Last Call: draft-ietf-ippm-initial-… Dale R. Worley
- Re: [ippm] WG Last Call: draft-ietf-ippm-initial-… Tommy Pauly
- Re: [ippm] WG Last Call: draft-ietf-ippm-initial-… tom petch
- Re: [ippm] WG Last Call: draft-ietf-ippm-initial-… MORTON, ALFRED C (AL)
- Re: [ippm] WG Last Call: draft-ietf-ippm-initial-… Tommy Pauly