draft-ietf-ippm-metric-registry-09.txt   draft-ietf-ippm-metric-registry-10.txt 
Network Working Group M. Bagnulo Network Working Group M. Bagnulo
Internet-Draft UC3M Internet-Draft UC3M
Intended status: Best Current Practice B. Claise Intended status: Best Current Practice B. Claise
Expires: May 3, 2017 Cisco Systems, Inc. Expires: June 3, 2017 Cisco Systems, Inc.
P. Eardley P. Eardley
BT BT
A. Morton A. Morton
AT&T Labs AT&T Labs
A. Akhter A. Akhter
Consultant Consultant
October 30, 2016 November 30, 2016
Registry for Performance Metrics Registry for Performance Metrics
draft-ietf-ippm-metric-registry-09 draft-ietf-ippm-metric-registry-10
Abstract Abstract
This document defines the format for the Performance Metrics registry This document defines the format for the Performance Metrics registry
and defines the IANA Registry for Performance Metrics. This document and defines the IANA Registry for Performance Metrics. This document
also gives a set of guidelines for Registered Performance Metric also gives a set of guidelines for Registered Performance Metric
requesters and reviewers. requesters and reviewers.
Status of This Memo Status of This Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 3, 2017. This Internet-Draft will expire on June 3, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 31 skipping to change at page 2, line 31
6. Performance Metric Registry: Prior attempt . . . . . . . . . 9 6. Performance Metric Registry: Prior attempt . . . . . . . . . 9
6.1. Why this Attempt Will Succeed . . . . . . . . . . . . . . 10 6.1. Why this Attempt Will Succeed . . . . . . . . . . . . . . 10
7. Definition of the Performance Metric Registry . . . . . . . . 10 7. Definition of the Performance Metric Registry . . . . . . . . 10
7.1. Summary Category . . . . . . . . . . . . . . . . . . . . 12 7.1. Summary Category . . . . . . . . . . . . . . . . . . . . 12
7.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 12 7.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 12
7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 13 7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 13
7.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 16 7.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 16
7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 16 7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 16
7.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 16 7.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 16
7.1.6. Change Controller . . . . . . . . . . . . . . . . . . 16 7.1.6. Change Controller . . . . . . . . . . . . . . . . . . 16
7.1.7. Version (of Registry Format) . . . . . . . . . . . . 16 7.1.7. Version (of Registry Format) . . . . . . . . . . . . 17
7.2. Metric Definition Category . . . . . . . . . . . . . . . 17 7.2. Metric Definition Category . . . . . . . . . . . . . . . 17
7.2.1. Reference Definition . . . . . . . . . . . . . . . . 17 7.2.1. Reference Definition . . . . . . . . . . . . . . . . 17
7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 17 7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 17
7.3. Method of Measurement Category . . . . . . . . . . . . . 18 7.3. Method of Measurement Category . . . . . . . . . . . . . 18
7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 18 7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 18
7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 18 7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 18
7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 19 7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 19
7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 19 7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 19
7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 20 7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 20
7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 20 7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 20
7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 21 7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 21
7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 21 7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 21
7.4.2. Reference Definition . . . . . . . . . . . . . . . . 21 7.4.2. Reference Definition . . . . . . . . . . . . . . . . 21
7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 21 7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 21
7.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 21 7.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 22
7.5. Administrative information . . . . . . . . . . . . . . . 22 7.5. Administrative information . . . . . . . . . . . . . . . 22
7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 22 7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 22
7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 22 7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 22
7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 22 7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 22
7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 22 7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 23
7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 23 7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 23
8. The Life-Cycle of Registered Performance Metrics . . . . . . 23 8. The Life-Cycle of Registered Performance Metrics . . . . . . 23
8.1. Adding new Performance Metrics to the Performance Metrics 8.1. Adding new Performance Metrics to the Performance Metrics
Registry . . . . . . . . . . . . . . . . . . . . . . . . 23 Registry . . . . . . . . . . . . . . . . . . . . . . . . 23
8.2. Revising Registered Performance Metrics . . . . . . . . . 24 8.2. Revising Registered Performance Metrics . . . . . . . . . 24
8.3. Deprecating Registered Performance Metrics . . . . . . . 25 8.3. Deprecating Registered Performance Metrics . . . . . . . 25
9. Security considerations . . . . . . . . . . . . . . . . . . . 26 9. Security considerations . . . . . . . . . . . . . . . . . . . 26
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 28
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
12.1. Normative References . . . . . . . . . . . . . . . . . . 28 12.1. Normative References . . . . . . . . . . . . . . . . . . 28
12.2. Informative References . . . . . . . . . . . . . . . . . 29 12.2. Informative References . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
The IETF specifies and uses Performance Metrics of protocols and The IETF specifies and uses Performance Metrics of protocols and
applications transported over its protocols. Performance metrics are applications transported over its protocols. Performance metrics are
such an important part of the operations of IETF protocols that such an important part of the operations of IETF protocols that
skipping to change at page 13, line 23 skipping to change at page 13, line 23
creating a new entry. creating a new entry.
Names are composed of the following elements, separated by an Names are composed of the following elements, separated by an
underscore character "_": underscore character "_":
MetricType_Method_SubTypeMethod_... Spec_Units_Output MetricType_Method_SubTypeMethod_... Spec_Units_Output
o MetricType: a combination of the directional properties and the o MetricType: a combination of the directional properties and the
metric measured, such as: metric measured, such as:
RTDelay RTDelay (Round Trip Delay)
RTDNS RTDNS (Response Time Domain Name Service)
OWDelay OWDelay (One Way Delay)
RTLoss RTLoss (Round Trip Loss)
OWLoss OWLoss (One Way Loss)
OWPDV OWPDV (One Way Packet Delay Variation)
OWIPDV OWIPDV (One Way Inter-Packet Delay Variation)
OWReorder OWReorder (One Way Packet Reordering)
OWDuplic OWDuplic (One Way Packet Duplication)
OWBTC OWBTC (One Way Bulk Transport Capacity)
OWMBM OWMBM (One Way Model Based Metric)
SPMonitor (Single Point Monitor) SPMonitor (Single Point Monitor)
MPMonitor (Multi-Point Monitor) MPMonitor (Multi-Point Monitor)
o Method: One of the methods defined in [RFC7799], such as: o Method: One of the methods defined in [RFC7799], such as:
Active Active (depends on a dedicated measurement packet stream and
Passive observations of the stream)
Passive (depends *solely* on observation of one or more
existing packet streams)
HybridType1 HybridType1 (obervations on one stream that combine both active
and passive methods)
HybridType2 HybridType2 (obervations on two or more streams that combine
both active and passive methods)
Spatial Spatial (Spatial Metric of RFC5644)
o SubTypeMethod: One or more sub-types to further describe the o SubTypeMethod: One or more sub-types to further describe the
features of the entry, such as: features of the entry, such as:
ICMP ICMP (Internet Control Message Protocol)
IP IP (Internet Protocol)
DSCPxx (where xx is replaced by a decimal code point) DSCPxx (where xx is replaced by a Diffserv code point)
UDP UDP (User Datagram Protocol)
TCP TCP (Transport Control Protocol)
Poisson Poisson (Packet generation using Poisson distribution)
Periodic Periodic (Periodic packet generation)
PayloadxxxxB (where xxxx is replaced by an integer) PayloadxxxxB (where xxxx is replaced by an integer, the number
of octets in the Payload))
SustainedBurst SustainedBurst (Capacity test, worst case)
StandingQueue StandingQueue (test of bottleneck queue behavior)
@@@@<add others from MBM draft?> @@@@<add others from MBM draft?>
SubTypeMethod values are separated by a hyphen "-" character, SubTypeMethod values are separated by a hyphen "-" character,
which indicates that they belong to this element, and that their which indicates that they belong to this element, and that their
order is unimportant when considering name uniqueness. order is unimportant when considering name uniqueness.
o Spec: RFC that specifies this entry in the form RFCXXXXsecY, such o Spec: RFC that specifies this entry in the form RFCXXXXsecY, such
as RFC7799sec3. Note: this is not the Primary Reference as RFC7799sec3. Note: this is not the Primary Reference
specification for the metric; it will be blank until the RFC specification for the metric; it will be blank until the RFC
skipping to change at page 15, line 4 skipping to change at page 15, line 8
as RFC7799sec3. Note: this is not the Primary Reference as RFC7799sec3. Note: this is not the Primary Reference
specification for the metric; it will be blank until the RFC specification for the metric; it will be blank until the RFC
number is assigned, and would remain blank in private registry number is assigned, and would remain blank in private registry
entries without an RFC. entries without an RFC.
o Units: The units of measurement for the output, such as: o Units: The units of measurement for the output, such as:
Seconds Seconds
RatioPercent (value multiplied by 100) RatioPercent (value multiplied by 100)
BPS (Bits per Second) BPS (Bits per Second)
EventTotal (for unit-less counts) EventTotal (for unit-less counts)
Multiple Multiple (more than one type of unit)
Enumerated Enumerated (a list of outcomes)
Unit-less Unit-less
o Output: The type of output resulting from measurement, such as: o Output: The type of output resulting from measurement, such as:
Singleton (sometimes called raw data) Singleton (sometimes called raw data)
Minimum Minimum
Maximum Maximum
Median Median
Mean Mean
95Percentile 95Percentile (95th Percentile)
99Percentile 99Percentile (99th Percentile)
StdDev StdDev (Standard Deviation)
Variance
PFI (Pass, Fail, Inconclusive) PFI (Pass, Fail, Inconclusive)
FlowRecords FlowRecords (descriptions of flows observed)
An example is: An example is:
RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95percentile RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95percentile
as described in section 4 of [I-D.ietf-ippm-initial-registry]. as described in section 4 of [I-D.ietf-ippm-initial-registry].
Note that private registries following the format described here Note that private registries following the format described here
SHOULD use the prefix "Priv_" on any name to avoid unintended SHOULD use the prefix "Priv_" on any name to avoid unintended
conflicts (further considerations are described in section 10). conflicts (further considerations are described in section 10).
skipping to change at page 15, line 45 skipping to change at page 16, line 4
An example is: An example is:
RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95percentile RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95percentile
as described in section 4 of [I-D.ietf-ippm-initial-registry]. as described in section 4 of [I-D.ietf-ippm-initial-registry].
Note that private registries following the format described here Note that private registries following the format described here
SHOULD use the prefix "Priv_" on any name to avoid unintended SHOULD use the prefix "Priv_" on any name to avoid unintended
conflicts (further considerations are described in section 10). conflicts (further considerations are described in section 10).
Private registry entries usually have no specifying RFC, thus the Private registry entries usually have no specifying RFC, thus the
Spec: element has no clear interpretation. Spec: element has no clear interpretation.
7.1.3. URIs 7.1.3. URIs
The URIs column MUST contain a URI [RFC3986] that uniquely identifies The URIs column MUST contain a URI [RFC3986] that uniquely identifies
the metric. This URI is a URN [RFC2141]. The URI is automatically the metric. This URI is a URN [RFC2141]. The URI is automatically
generated by prepending the prefix generated by prepending the prefix
urn:ietf:metric: urn:ietf:metric:perf:
to the metric name. The resulting URI is globally unique. to the metric name. The resulting URI is globally unique.
The URIs column MUST contain a second URI which is a URL [RFC3986] The URIs column MUST contain a second URI which is a URL [RFC3986]
and uniquely identifies and locates the metric entry so it is and uniquely identifies and locates the metric entry so it is
accessible through the Internet. The URL points to a file containing accessible through the Internet. The URL points to a file containing
the human-readable information of exactly one registry entry. the human-readable information of exactly one registry entry.
Ideally, the file will be HTML-formated and contain URLs to Ideally, the file will be HTML-formated and contain URLs to
referenced sections of HTML-ized RFCs. The separate files for referenced sections of HTML-ized RFCs. The separate files for
different entries can be more easily edited and re-used when different entries can be more easily edited and re-used when
skipping to change at page 27, line 41 skipping to change at page 27, line 45
Performance Metrics. Performance Metrics.
Extensions of the Registry require IETF Standards Action. Two forms Extensions of the Registry require IETF Standards Action. Two forms
of registry extension are envisaged: of registry extension are envisaged:
1. Adding columns or both categories and columns, to accommodate 1. Adding columns or both categories and columns, to accommodate
unanticipated aspects of new measurements and metric categories. unanticipated aspects of new measurements and metric categories.
2. Additional values for the various elements used in the Metric 2. Additional values for the various elements used in the Metric
"Name" column. A candidate Metric Entry RFC would propose one or "Name" column. A candidate Metric Entry RFC would propose one or
more new element values required to describe the entry. more new element values required to describe the entry, and the
values would be reviewed along with the metric entry.
To address this second point above, the IANA is asked to take the
sets of values for each name element in Section 7.1.2, and create a
sub-registry with the following columns:
MetricType:
Method:
SubTypeMethod:
Spec:
Units:
Output:
11. Acknowledgments 11. Acknowledgments
Thanks to Brian Trammell and Bill Cerveny, IPPM chairs, for leading Thanks to Brian Trammell and Bill Cerveny, IPPM chairs, for leading
some brainstorming sessions on this topic. Thanks to Barbara Stark some brainstorming sessions on this topic. Thanks to Barbara Stark
and Juergen Schoenwaelder for the detailed feedback and suggestions. and Juergen Schoenwaelder for the detailed feedback and suggestions.
Thanks to Andrew McGregor for suggestions on metric naming. Thanks Thanks to Andrew McGregor for suggestions on metric naming. Thanks
to Michelle Cotton for her early IANA review, and to Amanda Barber to Michelle Cotton for her early IANA review, and to Amanda Barber
for answering questions related to the presentation of the registry for answering questions related to the presentation of the registry
and accessibility of the complete template via URL. and accessibility of the complete template via URL.
skipping to change at page 31, line 18 skipping to change at page 31, line 37
DOI 10.17487/RFC7594, September 2015, DOI 10.17487/RFC7594, September 2015,
<http://www.rfc-editor.org/info/rfc7594>. <http://www.rfc-editor.org/info/rfc7594>.
[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with [RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799, Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,
May 2016, <http://www.rfc-editor.org/info/rfc7799>. May 2016, <http://www.rfc-editor.org/info/rfc7799>.
[I-D.ietf-ippm-initial-registry] [I-D.ietf-ippm-initial-registry]
Morton, A., Bagnulo, M., Eardley, P., and K. D'Souza, Morton, A., Bagnulo, M., Eardley, P., and K. D'Souza,
"Initial Performance Metric Registry Entries", draft-ietf- "Initial Performance Metric Registry Entries", draft-ietf-
ippm-initial-registry-01 (work in progress), July 2016. ippm-initial-registry-02 (work in progress), October 2016.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>. <http://www.rfc-editor.org/info/rfc6991>.
Authors' Addresses Authors' Addresses
Marcelo Bagnulo Marcelo Bagnulo
Universidad Carlos III de Madrid Universidad Carlos III de Madrid
Av. Universidad 30 Av. Universidad 30
Leganes, Madrid 28911 Leganes, Madrid 28911
SPAIN SPAIN
Phone: 34 91 6249500 Phone: 34 91 6249500
Email: marcelo@it.uc3m.es Email: marcelo@it.uc3m.es
URI: http://www.it.uc3m.es URI: http://www.it.uc3m.es
 End of changes. 45 change blocks. 
44 lines changed or deleted 69 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/