Network Working Group E. Stephan
Request for Comments: 4148 France Telecom R&D
BCP: 108 August 2005
Category: Best Current Practice
Network Working Group E. Stephan
Request for Comments: 4148 France Telecom R&D
BCP: 108 August 2005
Category: Best Current Practice
IP Performance Metrics (IPPM) Metrics Registry
IP性能度量（IPPM）度量注册表
Status of this Memo
本备忘录的状况
This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.
本文件规定了互联网社区的最佳现行做法，并要求进行讨论和提出改进建议。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This memo defines a registry for IP Performance Metrics (IPPM). It assigns and registers an initial set of OBJECT IDENTITIES to currently defined metrics in the IETF.
此备忘录定义了IP性能指标（IPPM）的注册表。它向IETF中当前定义的度量分配并注册一组初始对象标识。
This memo also defines the rules for adding IP Performance Metrics that are defined in the future and for encouraging all IP performance metrics to be registered here.
此备忘录还定义了添加将来定义的IP性能指标以及鼓励在此处注册所有IP性能指标的规则。
IANA has been assigned to administer this new registry.
IANA已被指定管理此新注册表。
Table of Contents
目录
1. The Internet-Standard Management Framework ......................2
2. Overview ........................................................2
3. IP Performance Metrics Registry Framework .......................2
4. Initial IPPM Metrics Registry Creation ..........................3
5. IANA Considerations .............................................4
5.1. Management Rules ...........................................4
5.2. Registration Template ......................................4
6. Initial IPPM Registry Definition ................................4
7. Security Considerations ........................................11
8. References .....................................................12
8.1. Normative References ......................................12
8.2. Informative References ....................................12
1. The Internet-Standard Management Framework ......................2
2. Overview ........................................................2
3. IP Performance Metrics Registry Framework .......................2
4. Initial IPPM Metrics Registry Creation ..........................3
5. IANA Considerations .............................................4
5.1. Management Rules ...........................................4
5.2. Registration Template ......................................4
6. Initial IPPM Registry Definition ................................4
7. Security Considerations ........................................11
8. References .....................................................12
8.1. Normative References ......................................12
8.2. Informative References ....................................12
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
This memo defines a registry of the current metrics and a framework for the integration of future metrics for the following reasons:
本备忘录定义了当前指标的注册和未来指标集成框架，原因如下：
o to permit metrics to be clearly referenced by MIB modules or other data models;
o 允许MIB模块或其他数据模型明确引用指标；
o to provide metrics identifiers for measurement interoperability;
o 为度量互操作性提供度量标识符；
o to take special care with the integration of future standardized metrics because it is a continuous process;
o 特别注意未来标准化指标的整合，因为这是一个持续的过程；
o to provide room where other standards bodies can register their metrics in order to encourage IP performance metrics to have OBJECT IDENTITIES rooted at a common point because the intent of the IPPM WG is to cooperate with other appropriate standards bodies (or fora) to promote consistent metrics;
o 为其他标准机构注册其指标提供空间，以鼓励IP性能指标将对象标识植根于共同点，因为IPPM工作组的目的是与其他适当的标准机构（或论坛）合作，以促进一致的指标；
o and, similarly, to provide room for enterprises to register metrics.
o 同样，为企业提供注册度量的空间。
MIB modules need to be able to reference IPPM Metrics precisely. The registry associates an OBJECT-IDENTITY with each metric. For example, Type-P-One-way-Delay and Type-P-One-way-Delay-Poisson-Stream have different OBJECT IDENTITIES.
MIB模块需要能够精确地引用IPPM度量。注册表将对象标识与每个度量相关联。例如，Type-P-One-way-Delay和Type-P-One-way-Delay-Poisson-Stream具有不同的对象标识。
The registry has one branch. Metrics are identified in the 'ianaIppmMetrics' subtree.
注册处有一个分支机构。指标在“IANAIPMMetrics”子树中确定。
This document defines an initial registry of the existing metrics defined in the IPPM WG and the rules to manage the registry.
本文件定义了IPPM工作组中定义的现有指标的初始注册表以及管理注册表的规则。
Documents defining metrics in the future will include in the IANA section the registration information to identify these metrics unambiguously.
未来定义指标的文件将在IANA部分包含注册信息，以明确识别这些指标。
The initial registry identifies the metrics currently defined in the RFCs produced in the IPPM WG. To date, the IPPM WG defined 33 metrics related to the following 7 topics:
初始注册表标识IPPM工作组中产生的RFC中当前定义的指标。迄今为止，IPPM工作组定义了与以下7个主题相关的33个指标：
1. IPPM Metrics for Measuring Connectivity, RFC 2678 [RFC2678]
1. IPPM测量连接性的指标，RFC 2678[RFC2678]
2. One-way Delay Metrics, RFC 2679 [RFC2679]
2. 单向延迟度量，RFC 2679[RFC2679]
3. One-way Packet Loss Metrics, RFC 2680 [RFC2680]
3. 单向分组丢失度量，RFC 2680[RFC2680]
4. Round-trip Delay Metrics, RFC 2681 [RFC2681]
4. 往返延迟度量，RFC 2681[RFC2681]
5. One-way Loss Pattern Sample Metrics, RFC 3357 [RFC3357]
5. 单向损失模式样本度量，RFC 3357[RFC3357]
6. IP Packet Delay Variation Metric, RFC 3393 [RFC3393]
6. IP包延迟变化度量，RFC 3393[RFC3393]
7. IPPM Metrics for periodic streams, RFC 3432 [RFC3432]
7. 周期流的IPPM度量，RFC 3432[RFC3432]
These are sequentially registered in the node ianaIppmMetrics.
它们在节点ianaIppmMetrics中顺序注册。
The naming conventions used for the existing metrics, and encouraged for new IPPM metrics, are:
用于现有指标和鼓励用于新IPPM指标的命名约定如下：
o Metrics names conform SMIv2 rules for descriptors defined in section 3.1 of [RFC2578];
o 度量名称符合[RFC2578]第3.1节中定义的描述符的SMIv2规则；
o The name starts with the prefix 'ietf';
o 名称以前缀“ietf”开头；
o 'Type-P' prefix is removed;
o 删除“Type-P”前缀；
o '-' are removed;
o 删除"一",；
o The letter following a '-' is changed to uppercase.
o “-”后面的字母改为大写。
This section describes the rules for the management of the registry by IANA.
本节介绍IANA管理注册表的规则。
Registrations are done sequentially by IANA in the ianaIppmMetrics subtree on the basis of 'Specification Required', as defined in [RFC2434].
IANA根据[RFC2434]中定义的“所需规范”，在ianaIppmMetrics子树中按顺序进行注册。
The reference of the specification must point to a stable document including a title, a revision, and a date.
规范的引用必须指向稳定的文档，包括标题、修订和日期。
The name always starts with the name of the organization and must respect the SMIv2 rules for descriptors defined in section 3.1 of [RFC2578].
名称始终以组织名称开头，并且必须遵守[RFC2578]第3.1节中定义的SMIv2描述符规则。
A document that creates new metrics would have an "IANA Considerations" section in which it would describe new metrics to be registered.
创建新指标的文档将有一个“IANA注意事项”部分，其中将描述要注册的新指标。
An OBJECT IDENTITY assigned to a metric is definitive and cannot be reused. If a new version of a metric is produced, then it is assigned with a new name and a new identifier.
分配给度量的对象标识是确定的，不能重复使用。如果生成了度量的新版本，则会为其分配新名称和新标识符。
The following is a proposed template to insert in the IANA considerations section. For each metric, that section would instantiate the following statement:
以下是拟插入IANA注意事项部分的模板。对于每个度量，该部分将实例化以下语句：
IANA has registed the following metric in the IANA-IPPM-METRICS-REGISTRY-MIB:
IANA已在IANA-IPPM-METRICS-REGISTRY-MIB中注册了以下指标：
aNewMetricName OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The identifier for a new metric."
REFERENCE
"Reference R, section n."
::= { ianaIppmMetrics nn } -- IANA assigns nn
aNewMetricName OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The identifier for a new metric."
REFERENCE
"Reference R, section n."
::= { ianaIppmMetrics nn } -- IANA assigns nn
IANA-IPPM-METRICS-REGISTRY-MIB DEFINITIONS ::= BEGIN
IANA-IPPM-METRICS-REGISTRY-MIB DEFINITIONS ::= BEGIN
IMPORTS
进口
OBJECT-IDENTITY, MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI;
SNMPv2 SMI中的对象标识、模块标识、mib-2；
ianaIppmMetricsRegistry MODULE-IDENTITY LAST-UPDATED "200507280000Z" -- July 28, 2005 ORGANIZATION "IANA" CONTACT-INFO "Internet Assigned Numbers Authority
IANAIPMMetricsRegistry MODULE-IDENTITY上次更新的“200507280000Z”-2005年7月28日组织“IANA”联系人信息“互联网分配号码管理局
Postal: ICANN 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292
邮政编码：ICANN 4676金钟路330号，加利福尼亚州玛丽娜·德雷，邮编90292
Tel: +1 310 823 9358
E-Mail: iana@iana.org"
Tel: +1 310 823 9358
E-Mail: iana@iana.org"
DESCRIPTION "This module defines a registry for IP Performance Metrics.
DESCRIPTION“此模块定义IP性能指标的注册表。
Registrations are done sequentially by IANA in the ianaIppmMetrics subtree on the basis of 'Specification Required', as defined in [RFC2434].
IANA根据[RFC2434]中定义的“所需规范”，在ianaIppmMetrics子树中按顺序进行注册。
The reference of the specification must point to a stable document including a title, a revision, and a date.
规范的引用必须指向稳定的文档，包括标题、修订和日期。
The name always starts with the name of the organization and must respect the SMIv2 rules for descriptors defined in section 3.1 of [RFC2578].
名称始终以组织名称开头，并且必须遵守[RFC2578]第3.1节中定义的SMIv2描述符规则。
A document that creates new metrics would have an IANA considerations section in which it would describe new metrics to be registered.
创建新指标的文档将有一个IANA注意事项部分，其中将描述要注册的新指标。
An OBJECT IDENTITY assigned to a metric is definitive and cannot be reused. If a new version of a metric is produced, then it is assigned with a new name and a new identifier.
分配给度量的对象标识是确定的，不能重复使用。如果生成了度量的新版本，则会为其分配新名称和新标识符。
Copyright (C) The Internet Society (2005). The initial version of
this MIB module was published in RFC 4148; for full legal notices
see the RFC itself or
http://www.ietf.org/copyrights/ianamib.html."
Copyright (C) The Internet Society (2005). The initial version of
this MIB module was published in RFC 4148; for full legal notices
see the RFC itself or
http://www.ietf.org/copyrights/ianamib.html."
REVISION "200507280000Z" -- July 28, 2005
DESCRIPTION
"Initial version of the IPPM metrics registry module.
This version published as RFC 4148."
::= { mib-2 128 }
REVISION "200507280000Z" -- July 28, 2005
DESCRIPTION
"Initial version of the IPPM metrics registry module.
This version published as RFC 4148."
::= { mib-2 128 }
ianaIppmMetrics OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Registration point for IP Performance Metrics."
::= { ianaIppmMetricsRegistry 1 }
ianaIppmMetrics OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Registration point for IP Performance Metrics."
::= { ianaIppmMetricsRegistry 1 }
-- -- Registry of the metrics of the IPPM WG RFCs --
--——IPPM工作组RFC指标登记册--
-- -- RFC 2678 "IPPM Metrics for Measuring Connectivity" --
----RFC 2678“测量连接性的IPPM度量”--
ietfInstantUnidirConnectivity OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Instantaneous-Unidirectional-Connectivity"
REFERENCE "RFC2678, section 2."
::= { ianaIppmMetrics 1}
ietfInstantUnidirConnectivity OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Instantaneous-Unidirectional-Connectivity"
REFERENCE "RFC2678, section 2."
::= { ianaIppmMetrics 1}
ietfInstantBidirConnectivity OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Instantaneous-Bidirectional-Connectivity"
REFERENCE "RFC2678, section 3."
::= { ianaIppmMetrics 2}
ietfInstantBidirConnectivity OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Instantaneous-Bidirectional-Connectivity"
REFERENCE "RFC2678, section 3."
::= { ianaIppmMetrics 2}
ietfIntervalUnidirConnectivity OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Interval-Unidirectional-Connectivity"
REFERENCE "RFC2678, section 4."
::= { ianaIppmMetrics 3 }
ietfIntervalUnidirConnectivity OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Interval-Unidirectional-Connectivity"
REFERENCE "RFC2678, section 4."
::= { ianaIppmMetrics 3 }
ietfIntervalBidirConnectivity OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Interval-Bidirectional-Connectivity"
REFERENCE "RFC2678, section 5."
::= { ianaIppmMetrics 4 }
ietfIntervalBidirConnectivity OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Interval-Bidirectional-Connectivity"
REFERENCE "RFC2678, section 5."
::= { ianaIppmMetrics 4 }
ietfIntervalTemporalConnectivity OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P1-P2-Interval-Temporal-Connectivity"
REFERENCE "RFC2678, section 6."
::= { ianaIppmMetrics 5 }
ietfIntervalTemporalConnectivity OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P1-P2-Interval-Temporal-Connectivity"
REFERENCE "RFC2678, section 6."
::= { ianaIppmMetrics 5 }
-- -- RFC 2679 "A One-way Delay Metric for IPPM" --
----RFC 2679“IPPM的单向延迟度量”--
ietfOneWayDelay OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay"
REFERENCE "RFC2679, section 3."
::= { ianaIppmMetrics 6 }
ietfOneWayDelay OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay"
REFERENCE "RFC2679, section 3."
::= { ianaIppmMetrics 6 }
ietfOneWayDelayPoissonStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Poisson-Stream"
REFERENCE "RFC2679, section 4."
::= { ianaIppmMetrics 7 }
ietfOneWayDelayPoissonStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Poisson-Stream"
REFERENCE "RFC2679, section 4."
::= { ianaIppmMetrics 7 }
ietfOneWayDelayPercentile OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Percentile"
REFERENCE "RFC2679, section 5.1."
::= { ianaIppmMetrics 8 }
ietfOneWayDelayPercentile OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Percentile"
REFERENCE "RFC2679, section 5.1."
::= { ianaIppmMetrics 8 }
ietfOneWayDelayMedian OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Median"
REFERENCE "RFC2679, section 5.2."
::= { ianaIppmMetrics 9 }
ietfOneWayDelayMedian OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Median"
REFERENCE "RFC2679, section 5.2."
::= { ianaIppmMetrics 9 }
ietfOneWayDelayMinimum OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Minimum"
REFERENCE "RFC2679, section 5.3."
::= { ianaIppmMetrics 10 }
ietfOneWayDelayMinimum OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Minimum"
REFERENCE "RFC2679, section 5.3."
::= { ianaIppmMetrics 10 }
ietfOneWayDelayInversePercentile OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Inverse-Percentile"
REFERENCE "RFC2679, section 5.4."
::= { ianaIppmMetrics 11 }
ietfOneWayDelayInversePercentile OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Inverse-Percentile"
REFERENCE "RFC2679, section 5.4."
::= { ianaIppmMetrics 11 }
-- -- RFC 2680 "One-way Packet Loss Metric for IPPM" --
----RFC 2680“IPPM的单向数据包丢失度量”--
ietfOneWayPktLoss OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Packet-Loss"
REFERENCE "RFC2680, section 2."
::= { ianaIppmMetrics 12 }
ietfOneWayPktLoss OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Packet-Loss"
REFERENCE "RFC2680, section 2."
::= { ianaIppmMetrics 12 }
ietfOneWayPktLossPoissonStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Packet-Loss-Poisson-Stream"
REFERENCE "RFC2680, section 3."
::= { ianaIppmMetrics 13 }
ietfOneWayPktLossPoissonStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Packet-Loss-Poisson-Stream"
REFERENCE "RFC2680, section 3."
::= { ianaIppmMetrics 13 }
ietfOneWayPktLossAverage OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Packet-Loss-Average"
REFERENCE "RFC2680, section 4."
::= { ianaIppmMetrics 14 }
ietfOneWayPktLossAverage OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Packet-Loss-Average"
REFERENCE "RFC2680, section 4."
::= { ianaIppmMetrics 14 }
-- -- RFC 2681 "A Round-trip Delay Metric for IPPM" --
----RFC 2681“IPPM的往返延迟度量”--
ietfRoundTripDelay OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Round-trip-Delay"
REFERENCE " section 2 of the rfc2681."
::= { ianaIppmMetrics 15 }
ietfRoundTripDelay OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Round-trip-Delay"
REFERENCE " section 2 of the rfc2681."
::= { ianaIppmMetrics 15 }
ietfRoundTripDelayPoissonStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Round-trip-Delay-Poisson-Stream"
REFERENCE "RFC2681, section 4."
::= { ianaIppmMetrics 16 }
ietfRoundTripDelayPoissonStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Round-trip-Delay-Poisson-Stream"
REFERENCE "RFC2681, section 4."
::= { ianaIppmMetrics 16 }
ietfRoundTripDelayPercentile OBJECT-IDENTITY STATUS current DESCRIPTION "Type-P-Round-trip-Delay-Percentile" REFERENCE "RFC2681, section 4.1."
ietfRoundTripDelayPercentile对象标识状态当前描述“P型往返延迟百分比”参考“RFC2681，第4.1节”
::= { ianaIppmMetrics 17 }
::= { ianaIppmMetrics 17 }
ietfRoundTripDelayMedian OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Round-trip-Delay-Median"
REFERENCE "RFC2681, section 4.2."
::= { ianaIppmMetrics 18 }
ietfRoundTripDelayMedian OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Round-trip-Delay-Median"
REFERENCE "RFC2681, section 4.2."
::= { ianaIppmMetrics 18 }
ietfRoundTripDelayMinimum OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Round-trip-Delay-Minimum"
REFERENCE "RFC2681, section 4.3."
::= { ianaIppmMetrics 19 }
ietfRoundTripDelayMinimum OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Round-trip-Delay-Minimum"
REFERENCE "RFC2681, section 4.3."
::= { ianaIppmMetrics 19 }
ietfRoundTripDelayInvPercentile OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Round-trip-Inverse-Percentile"
REFERENCE "RFC2681, section 4.4."
::= { ianaIppmMetrics 20 }
ietfRoundTripDelayInvPercentile OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-Round-trip-Inverse-Percentile"
REFERENCE "RFC2681, section 4.4."
::= { ianaIppmMetrics 20 }
-- -- RFC 3357: "One-way Loss Pattern Sample Metrics" --
----RFC 3357：“单向损失模式样本度量”--
ietfOneWayLossDistanceStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Loss-Distance-Stream"
REFERENCE " RFC3357, section 5.4.1."
::={ ianaIppmMetrics 21}
ietfOneWayLossDistanceStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Loss-Distance-Stream"
REFERENCE " RFC3357, section 5.4.1."
::={ ianaIppmMetrics 21}
ietfOneWayLossPeriodStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Loss-Period-Stream"
REFERENCE " RFC3357, section 5.4.2."
::={ ianaIppmMetrics 22}
ietfOneWayLossPeriodStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Loss-Period-Stream"
REFERENCE " RFC3357, section 5.4.2."
::={ ianaIppmMetrics 22}
ietfOneWayLossNoticeableRate OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Loss-Noticeable-Rate"
REFERENCE " RFC3357, section 6.1."
::= { ianaIppmMetrics 23 }
ietfOneWayLossNoticeableRate OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Loss-Noticeable-Rate"
REFERENCE " RFC3357, section 6.1."
::= { ianaIppmMetrics 23 }
ietfOneWayLossPeriodTotal OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Loss-Period-Total"
REFERENCE " RFC3357, section 6.2."
::= { ianaIppmMetrics 24 }
ietfOneWayLossPeriodTotal OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Loss-Period-Total"
REFERENCE " RFC3357, section 6.2."
::= { ianaIppmMetrics 24 }
ietfOneWayLossPeriodLengths OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Loss-Period-Lengths"
REFERENCE " RFC3357, section 6.3."
::= { ianaIppmMetrics 25 }
ietfOneWayLossPeriodLengths OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Loss-Period-Lengths"
REFERENCE " RFC3357, section 6.3."
::= { ianaIppmMetrics 25 }
ietfOneWayInterLossPeriodLengths OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Inter-Loss-Period-Lengths"
REFERENCE " RFC3357, section 6.4."
::= { ianaIppmMetrics 26 }
ietfOneWayInterLossPeriodLengths OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-Way-Inter-Loss-Period-Lengths"
REFERENCE " RFC3357, section 6.4."
::= { ianaIppmMetrics 26 }
--
-- RFC 3393: "IP Packet Delay Variation Metric
-- for IP Performance Metrics (IPPM)"
--
-- RFC 3393: "IP Packet Delay Variation Metric
-- for IP Performance Metrics (IPPM)"
ietfOneWayIpdv OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-ipdv"
REFERENCE " RFC3393, section 2."
::= { ianaIppmMetrics 27 }
ietfOneWayIpdv OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-ipdv"
REFERENCE " RFC3393, section 2."
::= { ianaIppmMetrics 27 }
ietfOneWayIpdvPoissonStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-ipdv-Poisson-stream"
REFERENCE " RFC3393, section 3."
::= { ianaIppmMetrics 28 }
ietfOneWayIpdvPoissonStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-ipdv-Poisson-stream"
REFERENCE " RFC3393, section 3."
::= { ianaIppmMetrics 28 }
ietfOneWayIpdvPercentile OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-ipdv-percentile"
REFERENCE " RFC3393, section 4.3."
::= { ianaIppmMetrics 29 }
ietfOneWayIpdvPercentile OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-ipdv-percentile"
REFERENCE " RFC3393, section 4.3."
::= { ianaIppmMetrics 29 }
ietfOneWayIpdvInversePercentile OBJECT-IDENTITY STATUS current
IETFonwayIPDVInversePercentile对象标识状态当前
DESCRIPTION
"Type-P-One-way-ipdv-inverse-percentile"
REFERENCE " RFC3393, section 4.4."
::= { ianaIppmMetrics 30 }
DESCRIPTION
"Type-P-One-way-ipdv-inverse-percentile"
REFERENCE " RFC3393, section 4.4."
::= { ianaIppmMetrics 30 }
ietfOneWayIpdvJitter OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-ipdv-jitter"
REFERENCE " RFC3393, section 4.5."
::= { ianaIppmMetrics 31 }
ietfOneWayIpdvJitter OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-ipdv-jitter"
REFERENCE " RFC3393, section 4.5."
::= { ianaIppmMetrics 31 }
ietfOneWayPeakToPeakIpdv OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-peak-to-peak-ipdv"
REFERENCE " RFC3393, section 4.6."
::= { ianaIppmMetrics 32 }
ietfOneWayPeakToPeakIpdv OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-peak-to-peak-ipdv"
REFERENCE " RFC3393, section 4.6."
::= { ianaIppmMetrics 32 }
-- -- RFC 3432: "Network performance measurement with periodic streams" --
----RFC 3432：“周期流网络性能测量”--
ietfOneWayDelayPeriodicStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Periodic-Stream"
REFERENCE " RFC3432, section 4."
::= { ianaIppmMetrics 33 }
ietfOneWayDelayPeriodicStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Type-P-One-way-Delay-Periodic-Stream"
REFERENCE " RFC3432, section 4."
::= { ianaIppmMetrics 33 }
END
终止
This module does not define any management objects. Instead, it assigns a set of OBJECT-IDENTITIES which may be used by other MIB modules to identify specific IP Performance Metrics.
此模块不定义任何管理对象。相反，它分配一组对象标识，其他MIB模块可以使用这些标识来识别特定的IP性能指标。
Meaningful security considerations can only be written in the MIB modules that define management objects. This document has therefore no impact on the security of the Internet.
有意义的安全注意事项只能写入定义管理对象的MIB模块中。因此，本文件对互联网的安全没有影响。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2678] Mahdavi, J. and V. Paxson, "IPPM Metrics for Measuring Connectivity", RFC 2678, September 1999.
[RFC2678]Mahdavi，J.和V.Paxson，“测量连接性的IPPM度量”，RFC 2678，1999年9月。
[RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way Delay Metric for IPPM", RFC 2679, September 1999.
[RFC2679]Almes，G.，Kalidini，S.，和M.Zekauskas，“IPPM的单向延迟度量”，RFC 2679，1999年9月。
[RFC2680] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way Packet Loss Metric for IPPM", RFC 2680, September 1999.
[RFC2680]Almes，G.，Kalidini，S.，和M.Zekauskas，“IPPM的单向数据包丢失度量”，RFC 2680，1999年9月。
[RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay Metric for IPPM", RFC 2681, September 1999.
[RFC2681]Almes，G.，Kalidini，S.，和M.Zekauskas，“IPPM的往返延迟度量”，RFC 2681，1999年9月。
[RFC3357] Koodli, R. and R. Ravikanth, "One-way Loss Pattern Sample Metrics", RFC 3357, August 2002.
[RFC3357]Koodli，R.和R.Ravikanth，“单向损失模式样本度量”，RFC 3357，2002年8月。
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)", RFC 3393, November 2002.
[RFC3393]Demichelis，C.和P.Chimento，“IP性能度量的IP数据包延迟变化度量（IPPM）”，RFC 3393，2002年11月。
[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network performance measurement with periodic streams", RFC 3432, November 2002.
[RFC3432]Raisanen，V.，Grotefeld，G.，和A.Morton，“周期流的网络性能测量”，RFC 3432，2002年11月。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
Author's Address
作者地址
Stephan Emile France Telecom R & D 2 avenue Pierre Marzin Lannion F-22307 France
Stephan Emile法国电信研发2大道Pierre Marzin Lannion F-22307法国
Fax: +33 2 96 05 18 52
EMail: emile.stephan@francetelecom.com
Fax: +33 2 96 05 18 52
EMail: emile.stephan@francetelecom.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。