draft-ietf-ippm-registry-active-00.txt | draft-ietf-ippm-registry-active-01.txt | |||
---|---|---|---|---|
Network Working Group A. Morton | Network Working Group A. Morton | |||
Internet-Draft AT&T Labs | Internet-Draft AT&T Labs | |||
Intended status: Standards Track M. Bagnulo | Intended status: Standards Track M. Bagnulo | |||
Expires: October 5, 2014 UC3M | Expires: January 5, 2015 UC3M | |||
P. Eardley | P. Eardley | |||
BT | BT | |||
April 3, 2014 | July 4, 2014 | |||
Active Performance Metric Sub-Registry | Active Performance Metric Sub-Registry | |||
draft-ietf-ippm-registry-active-00 | draft-ietf-ippm-registry-active-01 | |||
Abstract | Abstract | |||
This memo defines the Active Performance Metrics sub-registry of the | This memo defines the Active Performance Metrics sub-registry of the | |||
Performance Metric Registry. This sub-registry will contain Active | Performance Metric Registry. This sub-registry will contain Active | |||
Performance Metrics, especially those defined in RFCs prepared in the | Performance Metrics, especially those defined in RFCs prepared in the | |||
IP Performance Metrics (IPPM) Working Group of the IETF, and possibly | IP Performance Metrics (IPPM) Working Group of the IETF, and possibly | |||
applicable to other IETF metrics. Three aspects make IPPM metric | applicable to other IETF metrics. Three aspects make IPPM metric | |||
registration difficult: (1) Use of the Type-P notion to allow users | registration difficult: (1) Use of the Type-P notion to allow users | |||
to specify their own packet types. (2) Use of flexible input | to specify their own packet types. (2) Use of flexible input | |||
skipping to change at page 1, line 37 | skipping to change at page 1, line 37 | |||
stream of measurement packets. | stream of measurement packets. | |||
This memo proposes a way to organize registry entries into columns | This memo proposes a way to organize registry entries into columns | |||
that are well-defined, permitting consistent development of entries | that are well-defined, permitting consistent development of entries | |||
over time (a column may marked NA if it is not applicable for that | over time (a column may marked NA if it is not applicable for that | |||
metric). The design is intended to foster development of registry | metric). The design is intended to foster development of registry | |||
entries based on existing reference RFCs, whilst each column serves | entries based on existing reference RFCs, whilst each column serves | |||
as a check-list item to avoid omissions during the registration | as a check-list item to avoid omissions during the registration | |||
process. Every entry in the registry, before IANA action, requires | process. Every entry in the registry, before IANA action, requires | |||
Expert review as defined by concurrent IETF work in progress | Expert review as defined by concurrent IETF work in progress | |||
"Registry for Performance Metrics" (draft-manyfolks-ippm-metric- | "Registry for Performance Metrics" (draft-ietf-ippm-metric-registry). | |||
registry). | ||||
The document contains two examples: a registry entry for an active | The document contains two examples: a registry entry for an active | |||
Performance Metric entry based on RFC3393 and RFC5481, and a registry | Performance Metric entry based on RFC3393 and RFC5481, and a registry | |||
entry for an end-point Performance Metric based on RFC 7003. The | entry for an end-point Performance Metric based on RFC 7003. The | |||
examples are for Informational purposes and do not create any entry | examples are for Informational purposes and do not create any entry | |||
in the IANA registry. | in the IANA registry. | |||
Requirements Language | Requirements Language | |||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
skipping to change at page 2, line 26 | skipping to change at page 2, line 20 | |||
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 October 5, 2014. | This Internet-Draft will expire on January 5, 2015. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2014 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 48 | skipping to change at page 2, line 42 | |||
to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
described in the Simplified BSD License. | described in the Simplified BSD License. | |||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
1.1. Background and Motivation . . . . . . . . . . . . . . . . 5 | 1.1. Background and Motivation . . . . . . . . . . . . . . . . 5 | |||
2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 | 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
3. Registry Categories and Columns . . . . . . . . . . . . . . . 7 | 3. Registry Categories and Columns . . . . . . . . . . . . . . . 8 | |||
3.1. Common Registry Indexes and Information . . . . . . . . . 8 | 3.1. Common Registry Indexes and Information . . . . . . . . . 8 | |||
3.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 8 | 3.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 8 | |||
3.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 8 | 3.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 9 | |||
3.1.3. Status . . . . . . . . . . . . . . . . . . . . . . . 8 | 3.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 9 | |||
3.1.4. Requester . . . . . . . . . . . . . . . . . . . . . . 9 | 3.1.4. Status . . . . . . . . . . . . . . . . . . . . . . . 9 | |||
3.1.5. Revision . . . . . . . . . . . . . . . . . . . . . . 9 | 3.1.5. Requester . . . . . . . . . . . . . . . . . . . . . . 9 | |||
3.1.6. Revision Date . . . . . . . . . . . . . . . . . . . . 9 | 3.1.6. Revision . . . . . . . . . . . . . . . . . . . . . . 9 | |||
3.1.7. Description . . . . . . . . . . . . . . . . . . . . . 9 | 3.1.7. Revision Date . . . . . . . . . . . . . . . . . . . . 9 | |||
3.1.8. Reference Specification(s) . . . . . . . . . . . . . 9 | 3.1.8. Description . . . . . . . . . . . . . . . . . . . . . 9 | |||
3.1.9. Reference Specification(s) . . . . . . . . . . . . . 9 | ||||
3.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 9 | 3.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 9 | |||
3.2.1. Reference Definition . . . . . . . . . . . . . . . . 9 | 3.2.1. Reference Definition . . . . . . . . . . . . . . . . 9 | |||
3.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 9 | 3.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 10 | |||
3.3. Method of Measurement . . . . . . . . . . . . . . . . . . 10 | 3.3. Method of Measurement . . . . . . . . . . . . . . . . . . 10 | |||
3.3.1. Reference Method . . . . . . . . . . . . . . . . . . 10 | 3.3.1. Reference Method . . . . . . . . . . . . . . . . . . 10 | |||
3.3.2. Stream Type and Stream Parameters . . . . . . . . . . 10 | 3.3.2. Stream Type and Stream Parameters . . . . . . . . . . 10 | |||
3.3.3. Output Type and Data Format . . . . . . . . . . . . . 11 | 3.3.3. Output Type and Data Format . . . . . . . . . . . . . 11 | |||
3.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 11 | 3.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 11 | |||
3.3.5. Run-time Parameters and Data Format . . . . . . . . . 11 | 3.3.5. Run-time Parameters and Data Format . . . . . . . . . 12 | |||
3.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 12 | 3.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 12 | |||
4. Example IPPM Active Registry Entry . . . . . . . . . . . . . 12 | 4. Example IPPM Active Registry Entry . . . . . . . . . . . . . 12 | |||
4.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 12 | 4.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 12 | |||
4.1.1. Element ID . . . . . . . . . . . . . . . . . . . . . 12 | 4.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 12 | |||
4.1.2. Metric Name . . . . . . . . . . . . . . . . . . . . . 12 | 4.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 13 | |||
4.1.3. Metric Description . . . . . . . . . . . . . . . . . 12 | 4.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 13 | |||
4.1.4. Other Info Columns not provided in Example . . . . . 13 | 4.1.4. Status . . . . . . . . . . . . . . . . . . . . . . . 13 | |||
4.1.5. Requestor . . . . . . . . . . . . . . . . . . . . . . 13 | ||||
4.1.6. Revision . . . . . . . . . . . . . . . . . . . . . . 13 | ||||
4.1.7. Revision Date . . . . . . . . . . . . . . . . . . . . 13 | ||||
4.1.8. Description . . . . . . . . . . . . . . . . . . . . . 13 | ||||
4.1.9. Reference Specification(s) . . . . . . . . . . . . . 13 | ||||
4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 13 | 4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 13 | |||
4.2.1. Reference Definition . . . . . . . . . . . . . . . . 13 | 4.2.1. Reference Definition . . . . . . . . . . . . . . . . 13 | |||
4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 13 | 4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 14 | |||
4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 13 | 4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 14 | |||
4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 13 | 4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 14 | |||
4.3.2. Stream Type and Stream Parameters . . . . . . . . . . 13 | 4.3.2. Stream Type and Stream Parameters . . . . . . . . . . 14 | |||
4.3.3. Output Type and Data Format . . . . . . . . . . . . . 14 | 4.3.3. Output Type and Data Format . . . . . . . . . . . . . 14 | |||
4.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 14 | 4.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 15 | |||
4.3.5. Run-time Parameters and Data Format . . . . . . . . . 14 | 4.3.5. Run-time Parameters and Data Format . . . . . . . . . 15 | |||
4.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 15 | 4.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 16 | |||
5. Example RTCP-XR Registry Entry . . . . . . . . . . . . . . . 15 | 5. Example RTCP-XR Registry Entry . . . . . . . . . . . . . . . 16 | |||
5.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 15 | 5.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 16 | |||
5.1.1. Element ID . . . . . . . . . . . . . . . . . . . . . 16 | 5.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 16 | |||
5.1.2. Metric Name . . . . . . . . . . . . . . . . . . . . . 16 | 5.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 16 | |||
5.1.3. Metric Description . . . . . . . . . . . . . . . . . 16 | 5.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 16 | |||
5.1.4. Other Info Columns not provided in Example . . . . . 16 | 5.1.4. Status . . . . . . . . . . . . . . . . . . . . . . . 17 | |||
5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 16 | 5.1.5. Requestor . . . . . . . . . . . . . . . . . . . . . . 17 | |||
5.2.1. Reference Definition . . . . . . . . . . . . . . . . 16 | 5.1.6. Revision . . . . . . . . . . . . . . . . . . . . . . 17 | |||
5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 16 | 5.1.7. Revision Date . . . . . . . . . . . . . . . . . . . . 17 | |||
5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 17 | 5.1.8. Description . . . . . . . . . . . . . . . . . . . . . 17 | |||
5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 17 | 5.1.9. Reference Specification(s) . . . . . . . . . . . . . 17 | |||
5.3.2. Stream Type and Stream Parameters . . . . . . . . . . 17 | 5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 17 | |||
5.3.3. Output Type and Data Format . . . . . . . . . . . . . 18 | 5.2.1. Reference Definition . . . . . . . . . . . . . . . . 17 | |||
5.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 18 | 5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 17 | |||
5.3.5. Run-time Parameters and Data Format . . . . . . . . . 18 | 5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 18 | |||
5.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 20 | 5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 18 | |||
6. Example BLANK Registry Entry . . . . . . . . . . . . . . . . 20 | 5.3.2. Stream Type and Stream Parameters . . . . . . . . . . 19 | |||
6.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 20 | 5.3.3. Output Type and Data Format . . . . . . . . . . . . . 19 | |||
6.1.1. Element ID . . . . . . . . . . . . . . . . . . . . . 20 | 5.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 19 | |||
6.1.2. Metric Name . . . . . . . . . . . . . . . . . . . . . 20 | 5.3.5. Run-time Parameters and Data Format . . . . . . . . . 19 | |||
6.1.3. Metric Description . . . . . . . . . . . . . . . . . 20 | 5.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 21 | |||
6.1.4. Other Info Columns not provided in Example . . . . . 20 | 6. Example BLANK Registry Entry . . . . . . . . . . . . . . . . 21 | |||
6.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 20 | 6.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 21 | |||
6.2.1. Reference Definition . . . . . . . . . . . . . . . . 20 | 6.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 21 | |||
6.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 20 | 6.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 21 | |||
6.3. Method of Measurement . . . . . . . . . . . . . . . . . . 21 | 6.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 21 | |||
6.3.1. Reference Method . . . . . . . . . . . . . . . . . . 21 | 6.1.4. Status . . . . . . . . . . . . . . . . . . . . . . . 21 | |||
6.3.2. Stream Type and Stream Parameters . . . . . . . . . . 21 | 6.1.5. Requestor . . . . . . . . . . . . . . . . . . . . . . 21 | |||
6.3.3. Output Type and Data Format . . . . . . . . . . . . . 21 | 6.1.6. Revision . . . . . . . . . . . . . . . . . . . . . . 21 | |||
6.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 21 | 6.1.7. Revision Date . . . . . . . . . . . . . . . . . . . . 22 | |||
6.3.5. Run-time Parameters and Data Format . . . . . . . . . 21 | 6.1.8. Description . . . . . . . . . . . . . . . . . . . . . 22 | |||
6.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 22 | 6.1.9. Reference Specification(s) . . . . . . . . . . . . . 22 | |||
7. Security Considerations . . . . . . . . . . . . . . . . . . . 22 | 6.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 22 | |||
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 | 6.2.1. Reference Definition . . . . . . . . . . . . . . . . 22 | |||
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23 | 6.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 22 | |||
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 | 6.3. Method of Measurement . . . . . . . . . . . . . . . . . . 22 | |||
10.1. Normative References . . . . . . . . . . . . . . . . . . 23 | 6.3.1. Reference Method . . . . . . . . . . . . . . . . . . 22 | |||
10.2. Informative References . . . . . . . . . . . . . . . . . 24 | 6.3.2. Stream Type and Stream Parameters . . . . . . . . . . 22 | |||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 | 6.3.3. Output Type and Data Format . . . . . . . . . . . . . 23 | |||
6.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 23 | ||||
6.3.5. Run-time Parameters and Data Format . . . . . . . . . 23 | ||||
6.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 23 | ||||
7. Security Considerations . . . . . . . . . . . . . . . . . . . 23 | ||||
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 | ||||
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24 | ||||
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 24 | ||||
10.1. Normative References . . . . . . . . . . . . . . . . . . 25 | ||||
10.2. Informative References . . . . . . . . . . . . . . . . . 25 | ||||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 | ||||
1. Introduction | 1. Introduction | |||
[ISSUES | [ISSUES | |||
1. REAL-TIME OR INPUT PARAMETER [CONSISTENT WITH REGISTRY I-D] | 1. REAL-TIME OR INPUT PARAMETER [CONSISTENT WITH REGISTRY I-D] | |||
closed - just Parameter | closed - just Parameter | |||
2. CHANGED STREAM PARAMETER TO STREAM INPUT PARAMETER I didn't find | 2. CHANGED STREAM PARAMETER TO STREAM INPUT PARAMETER I didn't find | |||
any instances of this change - closed | any instances of this change - closed | |||
skipping to change at page 4, line 48 | skipping to change at page 5, line 11 | |||
4. RATHER THAN BLANK COLUMNS, SHOULD WE HAVE 'NOT APPLICABLE' [MAYBE | 4. RATHER THAN BLANK COLUMNS, SHOULD WE HAVE 'NOT APPLICABLE' [MAYBE | |||
EVEN IANA REGISTERED??] sounds good to Al, used NA. | EVEN IANA REGISTERED??] sounds good to Al, used NA. | |||
5. THE EXAMPLES ARE INFORMATIONAL NOT STANDARDS TRACK yes of course | 5. THE EXAMPLES ARE INFORMATIONAL NOT STANDARDS TRACK yes of course | |||
- -Closed. | - -Closed. | |||
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | |||
Note: Efforts to synchronize terminology with | Note: Efforts to synchronize terminology with | |||
[I-D.manyfolks-ippm-metric-registry] will likely be incomplete until | [I-D.ietf-ippm-metric-registry] will likely be incomplete until both | |||
both drafts are stable. | drafts are stable. | |||
This memo defines the Active Performance Metrics sub-registry of the | This memo defines the Active Performance Metrics sub-registry of the | |||
Performance Metric Registry. This sub-registry will contain Active | Performance Metric Registry. This sub-registry will contain Active | |||
Performance Metrics, especially those defined in RFCs prepared in the | Performance Metrics, especially those defined in RFCs prepared in the | |||
IP Performance Metrics (IPPM) Working Group of the IETF, according to | IP Performance Metrics (IPPM) Working Group of the IETF, according to | |||
their framework [RFC2330]. Three aspects make IPPM metric | their framework [RFC2330]. Three aspects make IPPM metric | |||
registration difficult: (1) Use of the Type-P notion to allow users | registration difficult: (1) Use of the Type-P notion to allow users | |||
to specify their own packet types. (2) Use of Flexible input | to specify their own packet types. (2) Use of Flexible input | |||
variables, called Parameters in IPPM definitions, some which | variables, called Parameters in IPPM definitions, some which | |||
determine the quantity measured and others which should not be | determine the quantity measured and others which should not be | |||
specified until execution of the measurement. (3) Allowing | specified until execution of the measurement. (3) Allowing | |||
flexibility in choice of statistics to summarize the results on a | flexibility in choice of statistics to summarize the results on a | |||
stream of measurement packets. This memo uses terms and definitions | stream of measurement packets. This memo uses terms and definitions | |||
from the IPPM literature, primarily [RFC2330], and the reader is | from the IPPM literature, primarily [RFC2330], and the reader is | |||
assumed familiar with them or may refer questions there as necessary. | assumed familiar with them or may refer questions there as necessary. | |||
This sub-registry is part of the Performance Metric Registry | This sub-registry is part of the Performance Metric Registry | |||
[I-D.manyfolks-ippm-metric-registry] which specifies that all sub- | [I-D.ietf-ippm-metric-registry] which specifies that all sub- | |||
registries must contain at least the following fields: the | registries must contain at least the following fields: the | |||
identifier, the name, the status, the requester, the revision, the | identifier, the name, the status, the requester, the revision, the | |||
revision date, the description for each entry, and the reference | revision date, the description for each entry, and the reference | |||
specifications used as the foundation for the Registered Performance | specifications used as the foundation for the Registered Performance | |||
Metric (see [I-D.manyfolks-ippm-metric-registry]). | Metric (see [I-D.ietf-ippm-metric-registry]). | |||
Although there are several standard templates for organizing | Although there are several standard templates for organizing | |||
specifications of performance metrics (see [RFC2679] for an example | specifications of performance metrics (see [RFC2679] for an example | |||
of the traditional IPPM template, based to large extent on the | of the traditional IPPM template, based to large extent on the | |||
Benchmarking Methodology Working Group's traditional template in | Benchmarking Methodology Working Group's traditional template in | |||
[RFC1242], and see [RFC6390] for a similar template), none of these | [RFC1242], and see [RFC6390] for a similar template), none of these | |||
templates was intended to become the basis for the columns of an | templates was intended to become the basis for the columns of an | |||
IETF-wide registry of metrics. As we examined the aspects of metric | IETF-wide registry of metrics. As we examined the aspects of metric | |||
specifications which need to be registered, it was clear that none of | specifications which need to be registered, it was clear that none of | |||
the existing metric templates fully satisfies the particular needs of | the existing metric templates fully satisfies the particular needs of | |||
skipping to change at page 6, line 19 | skipping to change at page 6, line 28 | |||
registry with only a few parameters open, if any. The idea is that | registry with only a few parameters open, if any. The idea is that | |||
entries in the registry represent different measurement methods. | entries in the registry represent different measurement methods. | |||
Each may require run-time parameters to set factors like source and | Each may require run-time parameters to set factors like source and | |||
destination addresses, which do not change the fundamental nature of | destination addresses, which do not change the fundamental nature of | |||
the measurement and can be set just before measurement execution. | the measurement and can be set just before measurement execution. | |||
The downside of this approach is that it could result in a large | The downside of this approach is that it could result in a large | |||
number of entries in the registry. We believe that less is more in | number of entries in the registry. We believe that less is more in | |||
this context - it is better to have a reduced set of useful metrics | this context - it is better to have a reduced set of useful metrics | |||
rather than a large set of metrics with questionable usefulness. | rather than a large set of metrics with questionable usefulness. | |||
Therefore it is required for all registries within the Performance | Therefore it is required for all registries within the Performance | |||
Metric Registry (see [I-D.manyfolks-ippm-metric-registry]) that the | Metric Registry (see [I-D.ietf-ippm-metric-registry]) that the | |||
registry only includes commonly used metrics that are well defined; | registry only includes commonly used metrics that are well defined; | |||
hence we require expert review policies for the approval and | hence we require expert review policies for the approval and | |||
assignment of entries in this sub-registry. | assignment of entries in this sub-registry. | |||
There are several side benefits of having a registry with well-chosen | There are several side benefits of having a registry with well-chosen | |||
entries. First, the registry could serve as an inventory of useful | entries. First, the registry could serve as an inventory of useful | |||
and used metrics that are normally supported by different | and used metrics that are normally supported by different | |||
implementations of measurement agents. Second, the results of the | implementations of measurement agents. Second, the results of the | |||
metrics would be comparable even if they are performed by different | metrics would be comparable even if they are performed by different | |||
implementations and in different networks, as the metric and method | implementations and in different networks, as the metric and method | |||
skipping to change at page 7, line 10 | skipping to change at page 7, line 19 | |||
consumer might want a one-off measurement made immediately to one | consumer might want a one-off measurement made immediately to one | |||
specific server; a regulator might want the same measurement made | specific server; a regulator might want the same measurement made | |||
once a day until further notice to the 'top 10' servers; whilst an | once a day until further notice to the 'top 10' servers; whilst an | |||
operator might want a varying series of tests (some of which will be | operator might want a varying series of tests (some of which will be | |||
beyond those defined in an IETF registry) as determined from time to | beyond those defined in an IETF registry) as determined from time to | |||
time by their operational support system. While the registries | time by their operational support system. While the registries | |||
defined in this document help to define the Characterization Plan, | defined in this document help to define the Characterization Plan, | |||
its full specification falls outside the scope of this document, and | its full specification falls outside the scope of this document, and | |||
other IETF work as currently chartered. | other IETF work as currently chartered. | |||
Note: Some operators of performance management systems will have the | ||||
capability to stop measurement activity on demand, and may benefit | ||||
from knowledge of recommended default behavior for the Metrics in the | ||||
active sub-registry. Since active methods of performance measurement | ||||
generate dedicated traffic, the default behavior should be to stop | ||||
measurement activity when requested by the management protocol. | ||||
2. Scope | 2. Scope | |||
[I-D.manyfolks-ippm-metric-registry] defines the overall structure | [I-D.ietf-ippm-metric-registry] defines the overall structure for a | |||
for a Performance Metric Registry and provides guidance for defining | Performance Metric Registry and provides guidance for defining a sub | |||
a sub registry. | registry. | |||
This document defines the Active Performance Metrics Sub-registry; | This document defines the Active Performance Metrics Sub-registry; | |||
active metrics are those where the packets measured have been | active metrics are those where the packets measured have been | |||
specially generated for the purpose. | specially generated for the purpose. | |||
A row in the registry corresponds to one Registered Performance | A row in the registry corresponds to one Registered Performance | |||
Metric, with entries in the various columns specifying the metric. | Metric, with entries in the various columns specifying the metric. | |||
Section 3 defines the columns for a Registered Active Performance | Section 3 defines the columns for a Registered Active Performance | |||
Metric. | Metric. | |||
As discussed in [I-D.manyfolks-ippm-metric-registry], each entry | As discussed in [I-D.ietf-ippm-metric-registry], each entry (row) | |||
(row) must be tightly defined; the definition must leave open only a | must be tightly defined; the definition must leave open only a few | |||
few parameters that do not change the fundamental nature of the | parameters that do not change the fundamental nature of the | |||
measurement (such as source and destination addresses), and so | measurement (such as source and destination addresses), and so | |||
promotes comparable results across independent implementations. | promotes comparable results across independent implementations. | |||
Also, each registered entry must be based on existing reference RFCs | Also, each registered entry must be based on existing reference RFCs | |||
(or other standards) for performance metrics, and must be | (or other standards) for performance metrics, and must be | |||
operationally useful and have significant industry interest. This is | operationally useful and have significant industry interest. This is | |||
ensured by expert review for every entry before IANA action. | ensured by expert review for every entry before IANA action. | |||
3. Registry Categories and Columns | 3. Registry Categories and Columns | |||
This section defines the categories and columns of the registry. | This section defines the categories and columns of the registry. | |||
skipping to change at page 8, line 28 | skipping to change at page 8, line 41 | |||
---------------------------------------------------------------- | ---------------------------------------------------------------- | |||
Reference Method | Stream Type | Output | Output | Run-time | | Reference Method | Stream Type | Output | Output | Run-time | | |||
| and Parameters | Type | Units | Param | | and Parameters | Type | Units | Param | |||
Comments and Remarks | Comments and Remarks | |||
-------------------- | -------------------- | |||
3.1. Common Registry Indexes and Information | 3.1. Common Registry Indexes and Information | |||
This category has multiple indexes to each registry entry. It is | This category has multiple indexes to each registry entry. It is | |||
defined in [I-D.manyfolks-ippm-metric-registry]: | defined in [I-D.ietf-ippm-metric-registry]: | |||
3.1.1. Identifier | 3.1.1. Identifier | |||
Defined in [I-D.manyfolks-ippm-metric-registry]. In order to have | Defined in [I-D.ietf-ippm-metric-registry]. In order to have the | |||
the document self contained, we could copy the definition from | document self contained, we could copy the definition from | |||
[I-D.manyfolks-ippm-metric-registry] here, but i guess we should do | [I-D.ietf-ippm-metric-registry] here, but i guess we should do that | |||
that once the definition in [I-D.manyfolks-ippm-metric-registry] is | once the definition in [I-D.ietf-ippm-metric-registry] is stable. | |||
stable. | ||||
3.1.2. Name | 3.1.2. Name | |||
Defined in [I-D.manyfolks-ippm-metric-registry], same comment than | Defined in [I-D.ietf-ippm-metric-registry], same comment than above. | |||
above. | ||||
3.1.3. Status | 3.1.3. URI | |||
Defined in [I-D.manyfolks-ippm-metric-registry], same comment than | Defined in [I-D.ietf-ippm-metric-registry], same comment than above. | |||
above. | ||||
3.1.4. Requester | 3.1.4. Status | |||
Defined in [I-D.manyfolks-ippm-metric-registry], same comment than | Defined in [I-D.ietf-ippm-metric-registry], same comment than above. | |||
above. | ||||
3.1.5. Revision | 3.1.5. Requester | |||
Defined in [I-D.manyfolks-ippm-metric-registry], same comment than | Defined in [I-D.ietf-ippm-metric-registry], same comment than above. | |||
above. | ||||
3.1.6. Revision Date | 3.1.6. Revision | |||
Defined in [I-D.manyfolks-ippm-metric-registry], same comment than | Defined in [I-D.ietf-ippm-metric-registry], same comment than above. | |||
above. | ||||
3.1.7. Description | 3.1.7. Revision Date | |||
Defined in [I-D.manyfolks-ippm-metric-registry], same comment as the | Defined in [I-D.ietf-ippm-metric-registry], same comment than above. | |||
3.1.8. Description | ||||
Defined in [I-D.ietf-ippm-metric-registry], same comment as the | ||||
previous. | previous. | |||
3.1.8. Reference Specification(s) | 3.1.9. Reference Specification(s) | |||
Defined in [I-D.manyfolks-ippm-metric-registry], same comment as the | Defined in [I-D.ietf-ippm-metric-registry], same comment as the | |||
previous. | previous. | |||
3.2. Metric Definition | 3.2. Metric Definition | |||
This category includes columns to prompt all necessary details | This category includes columns to prompt all necessary details | |||
related to the metric definition, including the RFC reference and | related to the metric definition, including the RFC reference and | |||
values of input factors, called fixed parameters, which are left open | values of input factors, called fixed parameters, which are left open | |||
in the RFC but have a particular value defined by the performance | in the RFC but have a particular value defined by the performance | |||
metric. | metric. | |||
skipping to change at page 12, line 35 | skipping to change at page 12, line 44 | |||
This section is Informational. | This section is Informational. | |||
This section gives an example registry entry for the active metric | This section gives an example registry entry for the active metric | |||
described in [RFC3393], on Packet Delay Variation. | described in [RFC3393], on Packet Delay Variation. | |||
4.1. Registry Indexes | 4.1. Registry Indexes | |||
This category includes multiple indexes to the registry entries, the | This category includes multiple indexes to the registry entries, the | |||
element ID and metric name. | element ID and metric name. | |||
4.1.1. Element ID | 4.1.1. Identifier | |||
An integer having enough digits to uniquely identify each entry in | An integer having enough digits to uniquely identify each entry in | |||
the Registry. | the Registry. | |||
4.1.2. Metric Name | 4.1.2. Name | |||
A metric naming convention is TBD. | A metric naming convention is TBD. | |||
One possibility based on IPPM's framework is: | One possibility based on IPPM's framework is: | |||
Act_IP-UDP-One-way-pdv-95th-percentile-Poisson | Act_IP-UDP-One-way-pdv-95th-percentile-Poisson | |||
4.1.3. Metric Description | 4.1.3. URI | |||
Prefix urn:ietf:params:performance:metric | ||||
4.1.4. Status | ||||
current | ||||
4.1.5. Requestor | ||||
Alcelip Mornuley | ||||
4.1.6. Revision | ||||
1.0 | ||||
4.1.7. Revision Date | ||||
2014-07-04 | ||||
4.1.8. Description | ||||
An assessment of packet delay variation with respect to the minimum | An assessment of packet delay variation with respect to the minimum | |||
delay observed on the stream. | delay observed on the stream. | |||
4.1.4. Other Info Columns not provided in Example | 4.1.9. Reference Specification(s) | |||
[RFC2330][RFC3393][RFC5481][RFC5905] | ||||
4.2. Metric Definition | 4.2. Metric Definition | |||
This category includes columns to prompt the entry of all necessary | This category includes columns to prompt the entry of all necessary | |||
details related to the metric definition, including the RFC reference | details related to the metric definition, including the RFC reference | |||
and values of input factors, called fixed parameters. | and values of input factors, called fixed parameters. | |||
4.2.1. Reference Definition | 4.2.1. Reference Definition | |||
See sections 2.4 and 3.4 of [RFC3393]. Singleton delay differences | See sections 2.4 and 3.4 of [RFC3393]. Singleton delay differences | |||
skipping to change at page 16, line 5 | skipping to change at page 16, line 39 | |||
This section gives an example registry entry for the end-point metric | This section gives an example registry entry for the end-point metric | |||
described in RFC 7003 [RFC7003], for RTCP-XR Burst/Gap Discard Metric | described in RFC 7003 [RFC7003], for RTCP-XR Burst/Gap Discard Metric | |||
reporting. | reporting. | |||
5.1. Registry Indexes | 5.1. Registry Indexes | |||
This category includes multiple indexes to the registry entries, the | This category includes multiple indexes to the registry entries, the | |||
element ID and metric name. | element ID and metric name. | |||
5.1.1. Element ID | 5.1.1. Identifier | |||
An integer having enough digits to uniquely identify each entry in | An integer having enough digits to uniquely identify each entry in | |||
the Registry. | the Registry. | |||
5.1.2. Metric Name | 5.1.2. Name | |||
A metric naming convention is TBD. | A metric naming convention is TBD. | |||
5.1.3. Metric Description | 5.1.3. URI | |||
Prefix urn:ietf:params:performance:metric | ||||
5.1.4. Status | ||||
current | ||||
5.1.5. Requestor | ||||
Alcelip Mornuley | ||||
5.1.6. Revision | ||||
1.0 | ||||
5.1.7. Revision Date | ||||
2014-07-04 | ||||
5.1.8. Description | ||||
TBD. | TBD. | |||
5.1.4. Other Info Columns not provided in Example | 5.1.9. Reference Specification(s) | |||
[RFC3611][RFC4566][RFC6776][RFC6792][RFC7003] | ||||
5.2. Metric Definition | 5.2. Metric Definition | |||
This category includes columns to prompt the entry of all necessary | This category includes columns to prompt the entry of all necessary | |||
details related to the metric definition, including the RFC reference | details related to the metric definition, including the RFC reference | |||
and values of input factors, called fixed parameters. Section 3.2 of | and values of input factors, called fixed parameters. Section 3.2 of | |||
[RFC7003] provides the reference information for this category. | [RFC7003] provides the reference information for this category. | |||
5.2.1. Reference Definition | 5.2.1. Reference Definition | |||
skipping to change at page 20, line 21 | skipping to change at page 21, line 26 | |||
This section is Informational. (?) | This section is Informational. (?) | |||
This section gives an example registry entry for the <type of metric | This section gives an example registry entry for the <type of metric | |||
and specification reference> . | and specification reference> . | |||
6.1. Registry Indexes | 6.1. Registry Indexes | |||
This category includes multiple indexes to the registry entries, the | This category includes multiple indexes to the registry entries, the | |||
element ID and metric name. | element ID and metric name. | |||
6.1.1. Element ID | 6.1.1. Identifier | |||
An integer having enough digits to uniquely identify each entry in | An integer. | |||
the Registry. | ||||
6.1.2. Metric Name | 6.1.2. Name | |||
A metric naming convention is TBD. | A metric naming convention is TBD. | |||
6.1.3. Metric Description | 6.1.3. URI | |||
A metric Description is TBD. | Prefix urn:ietf:params:performance:metric | |||
6.1.4. Other Info Columns not provided in Example | 6.1.4. Status | |||
current | ||||
6.1.5. Requestor | ||||
name or RFC, etc. | ||||
6.1.6. Revision | ||||
1.0 | ||||
6.1.7. Revision Date | ||||
YYYY-MM-DD | ||||
6.1.8. Description | ||||
TBD. | ||||
6.1.9. Reference Specification(s) | ||||
RFC... | ||||
6.2. Metric Definition | 6.2. Metric Definition | |||
This category includes columns to prompt the entry of all necessary | This category includes columns to prompt the entry of all necessary | |||
details related to the metric definition, including the RFC reference | details related to the metric definition, including the RFC reference | |||
and values of input factors, called fixed parameters. | and values of input factors, called fixed parameters. | |||
<possible section reference>. | <possible section reference>. | |||
6.2.1. Reference Definition | 6.2.1. Reference Definition | |||
skipping to change at page 22, line 17 | skipping to change at page 23, line 45 | |||
Additional (Informational) details for this entry | Additional (Informational) details for this entry | |||
7. Security Considerations | 7. Security Considerations | |||
This registry has no known implications on Internet Security. | This registry has no known implications on Internet Security. | |||
8. IANA Considerations | 8. IANA Considerations | |||
IANA is requested to create The Active Performance Metric Sub- | IANA is requested to create The Active Performance Metric Sub- | |||
registry within the Performance Metric Registry defined in | registry within the Performance Metric Registry defined in | |||
[I-D.manyfolks-ippm-metric-registry]. The Sub-registry will contain | [I-D.ietf-ippm-metric-registry]. The Sub-registry will contain the | |||
the following categories and (bullet) columns, (as defined in section | following categories and (bullet) columns, (as defined in section 3 | |||
3 above): | above): | |||
Common Registry Indexes and Info | Common Registry Indexes and Info | |||
o Identifier | o Identifier | |||
o Name | o Name | |||
o Status | o Status | |||
o Requester | o Requester | |||
o Revision | o Revision | |||
o Revision Date | o Revision Date | |||
skipping to change at page 23, line 14 | skipping to change at page 24, line 42 | |||
o Metric Units | o Metric Units | |||
o Run-time Parameters | o Run-time Parameters | |||
Comments and Remarks | Comments and Remarks | |||
9. Acknowledgements | 9. Acknowledgements | |||
The authors thank Brian Trammell for suggesting the term "Run-time | The authors thank Brian Trammell for suggesting the term "Run-time | |||
Parameters", which led to the distinction between run-time and fixed | Parameters", which led to the distinction between run-time and fixed | |||
parameters implemented in this memo, and the IPFIX metric with Flow | parameters implemented in this memo, for raising the IPFIX metric | |||
Key as an example. | with Flow Key as an example, and for many other productive | |||
suggestions. | ||||
10. References | 10. References | |||
10.1. Normative References | 10.1. Normative References | |||
[I-D.manyfolks-ippm-metric-registry] | [I-D.ietf-ippm-metric-registry] | |||
Bagnulo, M., Claise, B., Eardley, P., and A. Morton, | Bagnulo, M., Claise, B., Eardley, P., and A. Morton, | |||
"Registry for Performance Metrics", Internet Draft (work | "Registry for Performance Metrics", Internet Draft (work | |||
in progress) draft-manyfolks-ippm-metric-registry, 2014. | in progress) draft-ietf-ippm-metric-registry, 2014. | |||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
[RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, | [RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, | |||
"Framework for IP Performance Metrics", RFC 2330, May | "Framework for IP Performance Metrics", RFC 2330, May | |||
1998. | 1998. | |||
[RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way | [RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way | |||
Delay Metric for IPPM", RFC 2679, September 1999. | Delay Metric for IPPM", RFC 2679, September 1999. | |||
skipping to change at page 24, line 26 | skipping to change at page 26, line 9 | |||
10.2. Informative References | 10.2. Informative References | |||
[Brow00] Brownlee, N., "Packet Matching for NeTraMet | [Brow00] Brownlee, N., "Packet Matching for NeTraMet | |||
Distributions", March 2000. | Distributions", March 2000. | |||
[I-D.ietf-lmap-framework] | [I-D.ietf-lmap-framework] | |||
Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., | Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., | |||
Aitken, P., and A. Akhter, "A framework for large-scale | Aitken, P., and A. Akhter, "A framework for large-scale | |||
measurement platforms (LMAP)", draft-ietf-lmap- | measurement platforms (LMAP)", draft-ietf-lmap- | |||
framework-04 (work in progress), March 2014. | framework-07 (work in progress), June 2014. | |||
[RFC1242] Bradner, S., "Benchmarking terminology for network | [RFC1242] Bradner, S., "Benchmarking terminology for network | |||
interconnection devices", RFC 1242, July 1991. | interconnection devices", RFC 1242, July 1991. | |||
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control | ||||
Protocol Extended Reports (RTCP XR)", RFC 3611, November | ||||
2003. | ||||
[RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics | [RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics | |||
Registry", BCP 108, RFC 4148, August 2005. | Registry", BCP 108, RFC 4148, August 2005. | |||
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session | ||||
Description Protocol", RFC 4566, July 2006. | ||||
[RFC5472] Zseby, T., Boschi, E., Brownlee, N., and B. Claise, "IP | [RFC5472] Zseby, T., Boschi, E., Brownlee, N., and B. Claise, "IP | |||
Flow Information Export (IPFIX) Applicability", RFC 5472, | Flow Information Export (IPFIX) Applicability", RFC 5472, | |||
March 2009. | March 2009. | |||
[RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. | [RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. | |||
Carle, "Information Model for Packet Sampling Exports", | Carle, "Information Model for Packet Sampling Exports", | |||
RFC 5477, March 2009. | RFC 5477, March 2009. | |||
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation | [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation | |||
Applicability Statement", RFC 5481, March 2009. | Applicability Statement", RFC 5481, March 2009. | |||
[RFC6248] Morton, A., "RFC 4148 and the IP Performance Metrics | [RFC6248] Morton, A., "RFC 4148 and the IP Performance Metrics | |||
(IPPM) Registry of Metrics Are Obsolete", RFC 6248, April | (IPPM) Registry of Metrics Are Obsolete", RFC 6248, April | |||
2011. | 2011. | |||
[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New | [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New | |||
Performance Metric Development", BCP 170, RFC 6390, | Performance Metric Development", BCP 170, RFC 6390, | |||
October 2011. | October 2011. | |||
[RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information | ||||
Reporting Using a Source Description (SDES) Item and an | ||||
RTCP Extended Report (XR) Block", RFC 6776, October 2012. | ||||
[RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the | ||||
RTP Monitoring Framework", RFC 6792, November 2012. | ||||
[RFC7003] Clark, A., Huang, R., and Q. Wu, "RTP Control Protocol | [RFC7003] Clark, A., Huang, R., and Q. Wu, "RTP Control Protocol | |||
(RTCP) Extended Report (XR) Block for Burst/Gap Discard | (RTCP) Extended Report (XR) Block for Burst/Gap Discard | |||
Metric Reporting", RFC 7003, September 2013. | Metric Reporting", RFC 7003, September 2013. | |||
Authors' Addresses | Authors' Addresses | |||
Al Morton | Al Morton | |||
AT&T Labs | AT&T Labs | |||
200 Laurel Avenue South | 200 Laurel Avenue South | |||
Middletown,, NJ 07748 | Middletown,, NJ 07748 | |||
End of changes. 58 change blocks. | ||||
126 lines changed or deleted | 225 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |