draft-ietf-ippm-metrics-registry-07.txt   draft-ietf-ippm-metrics-registry-08.txt 
Network Working Group E. Stephan Network Working Group E. Stephan
Internet-Draft France Telecom R&D Internet-Draft France Telecom R&D
Expires: December 28, 2004 June 29, 2004 Expires: May 31, 2005 November 30, 2004
IP Performance Metrics (IPPM) metrics registry IP Performance Metrics (IPPM) metrics registry
draft-ietf-ippm-metrics-registry-07.txt draft-ietf-ippm-metrics-registry-08.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with and any of which I become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 33 skipping to change at page 1, line 32
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 28, 2004. This Internet-Draft will expire on May 31, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This memo defines a registry for IP Performance Metrics (IPPM). It This memo defines a registry for IP Performance Metrics (IPPM). It
assigns and registers an initial set of OBJECT IDENTITIES to assigns and registers an initial set of OBJECT IDENTITIES to
currently defined metrics in the IETF. currently defined metrics in the IETF.
This memo also defines the rules for adding new IP Performance This memo also defines the rules for adding new IP Performance
Metrics that are defined in the future. There are branches for other Metrics that are defined in the future and for encouraging all IP
standards bodies and enterprises defined to encourage all IP
performance metrics to be registered here. performance metrics to be registered here.
IANA has been assigned to administer this new registry. IANA has been assigned to administer this new registry.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . . 3 1. The Internet-Standard Management Framework . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IP Performance Metrics Registry Framework . . . . . . . . . . 3 3. IP Performance Metrics Registry Framework . . . . . . . . . . 3
4. Initial IPPM Metrics Registry Creation . . . . . . . . . . . . 4 4. Initial IPPM Metrics Registry Creation . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5.1 Management rules . . . . . . . . . . . . . . . . . . . . . 4 5.1 Management rules . . . . . . . . . . . . . . . . . . . . . 5
5.1.1 Naming Conventions . . . . . . . . . . . . . . . . . . 5 5.2 Registration template . . . . . . . . . . . . . . . . . . 5
5.1.2 Metrics Defined by IETF . . . . . . . . . . . . . . . 5 6. Initial IPPM registry definition . . . . . . . . . . . . . . . 6
5.1.3 Metrics Defined in Cooperation with Standards 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
bodies or Fora . . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1.4 Entreprise Metrics Registration . . . . . . . . . . . 6 8.1 Normative References . . . . . . . . . . . . . . . . . . . . 14
5.2 Registration templates . . . . . . . . . . . . . . . . . . 6 8.2 Informative References . . . . . . . . . . . . . . . . . . . 15
5.2.1 IETF RFCs . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 15
5.2.2 Standards bodies and Fora . . . . . . . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . 16
5.2.3 Enterprises . . . . . . . . . . . . . . . . . . . . . 7
6. Initial IPPM registry definition . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 16
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.1 Normative References . . . . . . . . . . . . . . . . . . . . 16
8.2 Informative References . . . . . . . . . . . . . . . . . . . 17
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . 18
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. Managed objects are accessed via a virtual RFC 3410 [RFC3410]. Managed objects are accessed via a virtual
information store, termed the Management Information Base or MIB. information store, termed the Management Information Base or MIB.
MIB objects are generally accessed through the Simple Network MIB objects are generally accessed through the Simple Network
Management Protocol (SNMP). Objects in the MIB are defined using the Management Protocol (SNMP). Objects in the MIB are defined using the
mechanisms defined in the Structure of Management Information (SMI). mechanisms defined in the Structure of Management Information (SMI).
skipping to change at page 3, line 27 skipping to change at page 3, line 27
2. Overview 2. Overview
This memo defines a registry of the current metrics and a framework This memo defines a registry of the current metrics and a framework
for the integration of future metrics for the following reasons: for the integration of future metrics for the following reasons:
o to permit metrics to be clearly referenced by MIB modules or other o to permit metrics to be clearly referenced by MIB modules or other
data models; data models;
o Metrics identifiers are needed to allow measurement o Metrics identifiers are needed to allow measurement
interoperability; As specification of new metrics is a continuous interoperability;
process, special care must be taken for the integration of future
standardized metrics; o As specification of new metrics is a continuous process, special
care must be taken for the integration of future standardized
metrics;
o Since the intent of the IPPM WG is to cooperate with other o Since the intent of the IPPM WG is to cooperate with other
appropriate standards bodies (or fora) to promote consistent appropriate standards bodies (or fora) to promote consistent
metrics, a branch where other standards bodies can register their metrics, room where other standards bodies can register their
metrics is provided to encourage IP performance metrics to have metrics is provided to encourage IP performance metrics to have
OBJECT IDENTITIES rooted at a common point; OBJECT IDENTITIES rooted at a common point;
o Similarly, a branch is provided for registered enterprises to o Similarly, room is provided for enterprises to register metrics.
register metrics.
3. IP Performance Metrics Registry Framework 3. IP Performance Metrics Registry Framework
MIB modules need to be able to precisely reference IPPM Metrics. The MIB modules need to be able to precisely reference IPPM Metrics. The
registry associates an OBJECT-IDENTITY with each metric. As an registry associates an OBJECT-IDENTITY with each metric. As an
example Type-P-One-way-Delay and Type-P-One-way-Delay-Poisson-Stream example Type-P-One-way-Delay and Type-P-One-way-Delay-Poisson-Stream
have different OBJECT IDENTITIES. have different OBJECT IDENTITIES.
The registry has 3 main branches. The origin of the document The registry has one branch. Metrics are identified in
defining the metrics determines the node which branch the metric is 'ianaIppmMetrics' subtree.
identified in:
o Metrics defined by IETF are identified in the
'ianaIppmIetfMetrics' tree;
o Metrics defined in cooperation with standards bodies or fora may
be identified in the 'ianaIppmForaMetrics' tree.
o Vendors may register private metrics in the
'ianaIppmEnterprisesMetrics' tree.
This document defines an initial registry of the existing metrics and This document defines an initial registry of the existing metrics
the rules to manage the registry. defined in the IPPM WG and the rules to manage the registry.
Documents defining metrics in the future will include in the IANA Documents defining metrics in the future will include in the IANA
section the registration information to unambiguously identify these section the registration information to unambiguously identify these
metrics. metrics.
4. Initial IPPM Metrics Registry Creation 4. Initial IPPM Metrics Registry Creation
The initial registry identifies the metrics currently defined in the The initial registry identifies the metrics currently defined in the
RFCs produced in the IPPM WG. To date, the IPPM WG defined 33 RFCs produced in the IPPM WG. To date, the IPPM WG defined 33
metrics related to 7 topics: metrics related to 7 topics:
skipping to change at page 4, line 39 skipping to change at page 4, line 30
o One-way Packet Loss Metrics, RFC 2680 [RFC2680]; o One-way Packet Loss Metrics, RFC 2680 [RFC2680];
o Round-trip Delay Metrics, RFC 2681 [RFC2681]; o Round-trip Delay Metrics, RFC 2681 [RFC2681];
o One-way Loss Pattern Sample Metrics, RFC 3357 [RFC3357]; o One-way Loss Pattern Sample Metrics, RFC 3357 [RFC3357];
o IP Packet Delay Variation Metric, RFC 3393 [RFC3393]; o IP Packet Delay Variation Metric, RFC 3393 [RFC3393];
o IPPM Metrics for periodic streams, RFC 3432 [RFC3432]; o IPPM Metrics for periodic streams, RFC 3432 [RFC3432];
5. IANA Considerations They are sequentially registered in the node ianaIppmMetrics.
This section describes the rules for the management of the registry
by IANA.
5.1 Management rules
Registrations are done by IANA on the bases of 'Specification
Required' as defined in [RFC2434].
The reference of the specification must point to a stable document
including a title, a revision and a date.
5.1.1 Naming Conventions
The name of the metric in the registry must respect the SMIv2 rules
for descriptors defined in the section 3.1 of [RFC2578]:
o Descriptors longer than 32 characters are not recommended;
o Initial character must be a lower-case letter;
o Hyphens are not allowed;
The following rules are applied to allocate the name and the
identifier of a metric:
o The name always starts with the name of the organization;
o OBJECT IDENTITIES for metrics are sequentially numbered by IANA;
o A OBJECT IDENTITY assigned to a metric is definitive and cannot be
reused;
o If a new version of a metric is produced then it is assigned with
a new name and a new identifier.
5.1.2 Metrics Defined by IETF The naming conventions used for the existing metrics, and encouraged
for new IPPM metrics, are :
Such metrics are registered in the node ianaIppmIetfMetrics(1). The o Metrics names comform SMIv2 rules for descriptors defined in the
guidelines used for the existing metrics, and encouraged for new section 3.1 of [RFC2578];
metrics, are
o The name always starts with the prefix 'ietf'. o The name starts with the prefix 'ietf';
o 'Type-P' prefix is removed. o 'Type-P' prefix is removed;
o '-' are removed; o '-' are removed;
o The letter following a '-' is changed to upper case; o The letter following a '-' is changed to upper case.
5.1.3 Metrics Defined in Cooperation with Standards bodies or Fora
IANA already assigns enterprises with unambiguous identifiers named
enterprise numbers or vendorID. See
http://www.iana.org/numbers.html.
o An organisation without an entreprise number should apply for one;
o IANA registers the metrics of an organisation under the branch
ianaIppmForaMetrics(2), in the subtree corresponding to its
enterprise number.
o The name of the metric always starts with (an abbreviation of) the
name of the organization.
For example, if the organisation ForumA has been assigned {
enterprises 696 }, it will register its metrics in the subtree
ianaIppmMetricsRegistry(x).ianaIppmForaMetrics(2).696. The name of a
metric starts with the prefix 'ForumA'.
Nothing prevents these bodies from registering metrics in their own
OBJECT INDENTIFIER trees.
5.1.4 Entreprise Metrics Registration
IANA already assigns enterprises with unambiguous identifiers named 5. IANA Considerations
enterprise numbers or vendorID. See
http://www.iana.org/numbers.html.
o An enterprise without an entreprise number should apply for one; This section describes the rules for the management of the registry
by IANA.
o IANA registers the metrics of an enterprise under the branch 5.1 Management rules
ianaIppmEnterprisesMetrics(3), in the subtree corresponding to its
enterprise number.
o The name of the metric always starts with (an abbreviation of) the Registrations are done sequentially by IANA in the ianaIppmMetrics
name of the company. subtree on the bases of 'Specification Required' as defined in
[RFC2434].
For example, if Acme Networks has been assigned { enterprises 696 }, The reference of the specification must point to a stable document
it will register its metrics in the subtree including a title, a revision and a date.
ianaIppmMetricsRegistry(x).ianaIppmEnterprisesMetrics(3).696. The
name of a metric starts with the prefix 'Acme'.
5.2 Registration templates The name always starts with the name of the organization and must
respect the SMIv2 rules for descriptors defined in the section 3.1 of
[RFC2578];
A document that creates new Metrics would have an IANA considerations A document that creates new metrics would have an IANA considerations
section in which it would describe new metrics to register. section in which it would describe new metrics to register.
5.2.1 IETF RFCs 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
For each metric, that section would have a statement aka: with a new name and a new identifier.
IANA has registed the following metric in the
IANA-IPPM-METRICS-REGISTRY-MIB:
ietfSomeNewMetricName OBJECT-IDENTITY
STATUS current
DESCRIPTION "The identifier for the Type-P-Some-New_Metric-Name
metric."
REFERENCE "RFCxxxx, section n." -- RFC-Editor fills in xxxx
::= { ianaIppmIetfMetrics nn } -- IANA assigns nn
5.2.2 Standards bodies and Fora
For each metric, that section would have a statement aka:
IANA has registed the following metric in the
IANA-IPPM-METRICS-REGISTRY-MIB:
foraNameSomeNewMetricName OBJECT-IDENTITY
STATUS current
DESCRIPTION "The identifier for the Some-New_Metric-Name
metric."
REFERENCE "Specification title/revision/date, section n."
::= { foraEnterpriseNumber nn } -- IANA assigns nn
5.2.3 Enterprises 5.2 Registration template
For each metric, that section would have a statement aka: Following is a proposed template to insert in the IANA considerations
section. For each metric, that section would instanciate the
following statement:
IANA has registed the following metric in the IANA has registed the following metric in the
IANA-IPPM-METRICS-REGISTRY-MIB: IANA-IPPM-METRICS-REGISTRY-MIB:
vendorNameSomeNewMetricName OBJECT-IDENTITY aNewMetricName OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The identifier for the Some-New_Metric-Name DESCRIPTION
metric." "The identifier for a new metric."
REFERENCE "Specification title/revision/date, section n." REFERENCE
::= { vendorEnterpriseNumber nn } -- IANA assigns nn "Reference R, section n."
::= { ianaIppmMetrics nn } -- IANA assigns nn
6. Initial IPPM registry definition 6. Initial IPPM registry definition
IANA-IPPM-METRICS-REGISTRY-MIB DEFINITIONS ::= BEGIN IANA-IPPM-METRICS-REGISTRY-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-IDENTITY, MODULE-IDENTITY, mib-2 OBJECT-IDENTITY, MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI; FROM SNMPv2-SMI;
ianaIppmMetricsRegistry MODULE-IDENTITY ianaIppmMetricsRegistry MODULE-IDENTITY
LAST-UPDATED "200406280000Z" -- June 28th, 2004 LAST-UPDATED "200411300000Z" -- November 30th, 2004
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO "Internet Assigned Numbers Authority CONTACT-INFO "Internet Assigned Numbers Authority
Postal: ICANN Postal: ICANN
4676 Admiralty Way, Suite 330 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292 Marina del Rey, CA 90292
Tel: +1 310 823 9358 Tel: +1 310 823 9358
E-Mail: iana@iana.org" E-Mail: iana@iana.org"
DESCRIPTION DESCRIPTION
"This module defines a registry for IP Performance (IPPM) Metrics. "This module defines a registry for IP Performance Metrics.
The registry is administred by IANA.
Following are the main rules for managing the registry:
* Registrations are done by IANA on the bases of 'Specification
Required' as defined in [RFC2434];
* Metrics names must comform SMIv2 rules for descriptors defined Registrations are done sequentially by IANA in the ianaIppmMetrics
in the section 3.1 of [RFC2578]; subtree on the bases of 'Specification Required' as defined in
[RFC2434].
* Metrics defined by IETF are registed by IANA in the The reference of the specification must point to a stable document
ianaIppmIetfMetrics subtree; including a title, a revision and a date.
* Metrics defined by a standards bodies are registed by IANA The name always starts with the name of the organization and must
under the node corresponding to the entreprise number of this respect the SMIv2 rules for descriptors defined in the section 3.1
organisation in the ianaIppmForaMetrics subtree; of [RFC2578];
* Metrics defined by an enterprise are registed by IANA under the A document that creates new metrics would have an IANA
node corresponding to the entreprise number of this company in considerations section in which it would describe new metrics to
the ianaIppmEnterprisesMetrics subtree; register.
The rules are fully described in the 'IANA considerations' An OBJECT IDENTITY assigned to a metric is definitive and cannot
section. 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 (2004). The initial version of Copyright (C) The Internet Society (2004). The initial version of
this MIB module was published in RFC yyyy; for full legal notices this MIB module was published in RFC yyyy; for full legal notices
see the RFC itself or see: see the RFC itself or see:
http://www.ietf.org/copyrights/ianamib.html. " http://www.ietf.org/copyrights/ianamib.html. "
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200406280000Z" -- June 28th, 2004 REVISION "200411300000Z" -- November 30th, 2004
DESCRIPTION DESCRIPTION
"Initial version of the IPPM metrics registry module. "Initial version of the IPPM metrics registry module.
This version published as RFC yyyy." This version published as RFC yyyy."
::= { mib-2 XXX } -- XXX to be assigned by IANA ::= { mib-2 XXX } -- XXX to be assigned by IANA
ianaIppmIetfMetrics OBJECT-IDENTITY ianaIppmMetrics OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Registration point for IP Performance (IPPM) Metrics "Registration point for IP Performance Metrics."
defined by the IETF."
::= { ianaIppmMetricsRegistry 1 } ::= { ianaIppmMetricsRegistry 1 }
ianaIppmForaMetrics OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Registration point for IP Performance Metrics
defined by other (i.e., non-IETF) organizations."
::= { ianaIppmMetricsRegistry 2 }
ianaIppmEnterprisesMetrics OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Registration point for IP Performance Metrics
defined by enterprises or vendors."
::= { ianaIppmMetricsRegistry 3 }
-- --
-- Registry of the metrics of the IPPM WG RFCs -- Registry of the metrics of the IPPM WG RFCs
-- --
-- --
-- RFC 2678 " IPPM Metrics for Measuring Connectivity" -- RFC 2678 " IPPM Metrics for Measuring Connectivity"
-- --
ietfInstantUnidirConnectivity OBJECT-IDENTITY ietfInstantUnidirConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-Instantaneous-Unidirectional-Connectivity" "Type-P-Instantaneous-Unidirectional-Connectivity"
REFERENCE "RFC2678, section 2." REFERENCE "RFC2678, section 2."
::= { ianaIppmIetfMetrics 1} ::= { ianaIppmMetrics 1}
ietfInstantBidirConnectivity OBJECT-IDENTITY ietfInstantBidirConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-Instantaneous-Bidirectional-Connectivity" "Type-P-Instantaneous-Bidirectional-Connectivity"
REFERENCE "RFC2678, section 3." REFERENCE "RFC2678, section 3."
::= { ianaIppmIetfMetrics 2} ::= { ianaIppmMetrics 2}
ietfIntervalUnidirConnectivity OBJECT-IDENTITY ietfIntervalUnidirConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-Interval-Unidirectional-Connectivity" "Type-P-Interval-Unidirectional-Connectivity"
REFERENCE "RFC2678, section 4." REFERENCE "RFC2678, section 4."
::= { ianaIppmIetfMetrics 3 } ::= { ianaIppmMetrics 3 }
ietfIntervalBidirConnectivity OBJECT-IDENTITY ietfIntervalBidirConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-Interval-Bidirectional-Connectivity" "Type-P-Interval-Bidirectional-Connectivity"
REFERENCE "RFC2678, section 5." REFERENCE "RFC2678, section 5."
::= { ianaIppmIetfMetrics 4 } ::= { ianaIppmMetrics 4 }
ietfIntervalTemporalConnectivity OBJECT-IDENTITY ietfIntervalTemporalConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P1-P2-Interval-Temporal-Connectivity" "Type-P1-P2-Interval-Temporal-Connectivity"
REFERENCE "RFC2678, section 6." REFERENCE "RFC2678, section 6."
::= { ianaIppmIetfMetrics 5 } ::= { ianaIppmMetrics 5 }
-- --
-- RFC 2679 "A One-way Delay Metric for IPPM" -- RFC 2679 "A One-way Delay Metric for IPPM"
-- --
ietfOneWayDelay OBJECT-IDENTITY ietfOneWayDelay OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-Delay" "Type-P-One-way-Delay"
REFERENCE "RFC2679, section 3." REFERENCE "RFC2679, section 3."
::= { ianaIppmIetfMetrics 6 } ::= { ianaIppmMetrics 6 }
ietfOneWayDelayPoissonStream OBJECT-IDENTITY ietfOneWayDelayPoissonStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-Delay-Poisson-Stream" "Type-P-One-way-Delay-Poisson-Stream"
REFERENCE "RFC2679, section 4." REFERENCE "RFC2679, section 4."
::= { ianaIppmIetfMetrics 7 } ::= { ianaIppmMetrics 7 }
ietfOneWayDelayPercentile OBJECT-IDENTITY ietfOneWayDelayPercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-Delay-Percentile" "Type-P-One-way-Delay-Percentile"
REFERENCE "RFC2679, section 5.1." REFERENCE "RFC2679, section 5.1."
::= { ianaIppmIetfMetrics 8 } ::= { ianaIppmMetrics 8 }
ietfOneWayDelayMedian OBJECT-IDENTITY ietfOneWayDelayMedian OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-Delay-Median" "Type-P-One-way-Delay-Median"
REFERENCE "RFC2679, section 5.2." REFERENCE "RFC2679, section 5.2."
::= { ianaIppmIetfMetrics 9 } ::= { ianaIppmMetrics 9 }
ietfOneWayDelayMinimum OBJECT-IDENTITY ietfOneWayDelayMinimum OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-Delay-Minimum" "Type-P-One-way-Delay-Minimum"
REFERENCE "RFC2679, section 5.3." REFERENCE "RFC2679, section 5.3."
::= { ianaIppmIetfMetrics 10 } ::= { ianaIppmMetrics 10 }
ietfOneWayDelayInversePercentile OBJECT-IDENTITY ietfOneWayDelayInversePercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-Delay-Inverse-Percentile" "Type-P-One-way-Delay-Inverse-Percentile"
REFERENCE "RFC2679, section 5.4." REFERENCE "RFC2679, section 5.4."
::= { ianaIppmIetfMetrics 11 } ::= { ianaIppmMetrics 11 }
-- --
-- RFC 2680 "One Way Packet Loss Metric for IPPM" -- RFC 2680 "One Way Packet Loss Metric for IPPM"
-- --
ietfOneWayPktLoss OBJECT-IDENTITY ietfOneWayPktLoss OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-Packet-Loss" "Type-P-One-way-Packet-Loss"
REFERENCE "RFC2680, section 2." REFERENCE "RFC2680, section 2."
::= { ianaIppmIetfMetrics 12 } ::= { ianaIppmMetrics 12 }
ietfOneWayPktLossPoissonStream OBJECT-IDENTITY ietfOneWayPktLossPoissonStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-Packet-Loss-Poisson-Stream" "Type-P-One-way-Packet-Loss-Poisson-Stream"
REFERENCE "RFC2680, section 3." REFERENCE "RFC2680, section 3."
::= { ianaIppmIetfMetrics 13 } ::= { ianaIppmMetrics 13 }
ietfOneWayPktLossAverage OBJECT-IDENTITY ietfOneWayPktLossAverage OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-Packet-Loss-Average" "Type-P-One-way-Packet-Loss-Average"
REFERENCE "RFC2680, section 4." REFERENCE "RFC2680, section 4."
::= { ianaIppmIetfMetrics 14 } ::= { ianaIppmMetrics 14 }
-- --
-- RFC2681 "A Round-trip Delay Metric for IPPM" -- RFC2681 "A Round-trip Delay Metric for IPPM"
-- --
ietfRoundTripDelay OBJECT-IDENTITY ietfRoundTripDelay OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-Round-trip-Delay" "Type-P-Round-trip-Delay"
REFERENCE " section 2 of the rfc2681." REFERENCE " section 2 of the rfc2681."
::= { ianaIppmIetfMetrics 15 } ::= { ianaIppmMetrics 15 }
ietfRoundTripDelayPoissonStream OBJECT-IDENTITY ietfRoundTripDelayPoissonStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-Round-trip-Delay-Poisson-Stream" "Type-P-Round-trip-Delay-Poisson-Stream"
REFERENCE "RFC2681, section 4." REFERENCE "RFC2681, section 4."
::= { ianaIppmIetfMetrics 16 } ::= { ianaIppmMetrics 16 }
ietfRoundTripDelayPercentile OBJECT-IDENTITY ietfRoundTripDelayPercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-Round-trip-Delay-Percentile" "Type-P-Round-trip-Delay-Percentile"
REFERENCE "RFC2681, section 4.1." REFERENCE "RFC2681, section 4.1."
::= { ianaIppmIetfMetrics 17 } ::= { ianaIppmMetrics 17 }
ietfRoundTripDelayMedian OBJECT-IDENTITY ietfRoundTripDelayMedian OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-Round-trip-Delay-Median" "Type-P-Round-trip-Delay-Median"
REFERENCE "RFC2681, section 4.2." REFERENCE "RFC2681, section 4.2."
::= { ianaIppmIetfMetrics 18 } ::= { ianaIppmMetrics 18 }
ietfRoundTripDelayMinimum OBJECT-IDENTITY ietfRoundTripDelayMinimum OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-Round-trip-Delay-Minimum" "Type-P-Round-trip-Delay-Minimum"
REFERENCE "RFC2681, section 4.3." REFERENCE "RFC2681, section 4.3."
::= { ianaIppmIetfMetrics 19 } ::= { ianaIppmMetrics 19 }
ietfRoundTripDelayInvPercentile OBJECT-IDENTITY ietfRoundTripDelayInvPercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-Round-trip-Inverse-Percentile" "Type-P-Round-trip-Inverse-Percentile"
REFERENCE "RFC2681, section 4.4." REFERENCE "RFC2681, section 4.4."
::= { ianaIppmIetfMetrics 20 } ::= { ianaIppmMetrics 20 }
-- --
-- RFC3357: "One-way Loss Pattern Sample Metrics" -- RFC3357: "One-way Loss Pattern Sample Metrics"
-- --
ietfOneWayLossDistanceStream OBJECT-IDENTITY ietfOneWayLossDistanceStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-Way-Loss-Distance-Stream" "Type-P-One-Way-Loss-Distance-Stream"
REFERENCE " RFC3357, section 5.4.1." REFERENCE " RFC3357, section 5.4.1."
::={ ianaIppmIetfMetrics 21} ::={ ianaIppmMetrics 21}
ietfOneWayLossPeriodStream OBJECT-IDENTITY ietfOneWayLossPeriodStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-Way-Loss-Period-Stream" "Type-P-One-Way-Loss-Period-Stream"
REFERENCE " RFC3357, section 5.4.2." REFERENCE " RFC3357, section 5.4.2."
::={ ianaIppmIetfMetrics 22} ::={ ianaIppmMetrics 22}
ietfOneWayLossNoticeableRate OBJECT-IDENTITY ietfOneWayLossNoticeableRate OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-Way-Loss-Noticeable-Rate" "Type-P-One-Way-Loss-Noticeable-Rate"
REFERENCE " RFC3357, section 6.1." REFERENCE " RFC3357, section 6.1."
::= { ianaIppmIetfMetrics 23 } ::= { ianaIppmMetrics 23 }
ietfOneWayLossPeriodTotal OBJECT-IDENTITY ietfOneWayLossPeriodTotal OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-Way-Loss-Period-Total" "Type-P-One-Way-Loss-Period-Total"
REFERENCE " RFC3357, section 6.2." REFERENCE " RFC3357, section 6.2."
::= { ianaIppmIetfMetrics 24 } ::= { ianaIppmMetrics 24 }
ietfOneWayLossPeriodLengths OBJECT-IDENTITY ietfOneWayLossPeriodLengths OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-Way-Loss-Period-Lengths" "Type-P-One-Way-Loss-Period-Lengths"
REFERENCE " RFC3357, section 6.3." REFERENCE " RFC3357, section 6.3."
::= { ianaIppmIetfMetrics 25 } ::= { ianaIppmMetrics 25 }
ietfOneWayInterLossPeriodLengths OBJECT-IDENTITY ietfOneWayInterLossPeriodLengths OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-Way-Inter-Loss-Period-Lengths" "Type-P-One-Way-Inter-Loss-Period-Lengths"
REFERENCE " RFC3357, section 6.4." REFERENCE " RFC3357, section 6.4."
::= { ianaIppmIetfMetrics 26 } ::= { ianaIppmMetrics 26 }
-- --
-- RFC3393: -- RFC3393:
-- IP Packet Delay Variation Metric for IP Performance Metrics (IPPM) -- IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)
ietfOneWayIpdv OBJECT-IDENTITY ietfOneWayIpdv OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-ipdv" "Type-P-One-way-ipdv"
REFERENCE " RFC3393, section 2." REFERENCE " RFC3393, section 2."
::= { ianaIppmIetfMetrics 27 } ::= { ianaIppmMetrics 27 }
ietfOneWayIpdvPoissonStream OBJECT-IDENTITY ietfOneWayIpdvPoissonStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-ipdv-Poisson-stream" "Type-P-One-way-ipdv-Poisson-stream"
REFERENCE " RFC3393, section 3." REFERENCE " RFC3393, section 3."
::= { ianaIppmIetfMetrics 28 } ::= { ianaIppmMetrics 28 }
ietfOneWayIpdvPercentile OBJECT-IDENTITY ietfOneWayIpdvPercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-ipdv-percentile" "Type-P-One-way-ipdv-percentile"
REFERENCE " RFC3393, section 4.3." REFERENCE " RFC3393, section 4.3."
::= { ianaIppmIetfMetrics 29 } ::= { ianaIppmMetrics 29 }
ietfOneWayIpdvInversePercentile OBJECT-IDENTITY ietfOneWayIpdvInversePercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-ipdv-inverse-percentile" "Type-P-One-way-ipdv-inverse-percentile"
REFERENCE " RFC3393, section 4.4." REFERENCE " RFC3393, section 4.4."
::= { ianaIppmIetfMetrics 30 } ::= { ianaIppmMetrics 30 }
ietfOneWayIpdvJitter OBJECT-IDENTITY ietfOneWayIpdvJitter OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-ipdv-jitter" "Type-P-One-way-ipdv-jitter"
REFERENCE " RFC3393, section 4.5." REFERENCE " RFC3393, section 4.5."
::= { ianaIppmIetfMetrics 31 } ::= { ianaIppmMetrics 31 }
ietfOneWayPeakToPeakIpdv OBJECT-IDENTITY ietfOneWayPeakToPeakIpdv OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-peak-to-peak-ipdv" "Type-P-One-way-peak-to-peak-ipdv"
REFERENCE " RFC3393, section 4.6." REFERENCE " RFC3393, section 4.6."
::= { ianaIppmIetfMetrics 32 } ::= { ianaIppmMetrics 32 }
-- --
-- RFC3432: "Network performance measurement with periodic streams" -- RFC3432: "Network performance measurement with periodic streams"
-- --
ietfOneWayDelayPeriodicStream OBJECT-IDENTITY ietfOneWayDelayPeriodicStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type-P-One-way-Delay-Periodic-Stream" "Type-P-One-way-Delay-Periodic-Stream"
REFERENCE " RFC3432, section 4." REFERENCE " RFC3432, section 4."
::= { ianaIppmIetfMetrics 33 } ::= { ianaIppmMetrics 33 }
END END
7. Security Considerations 7. Security Considerations
This module does not define any management objects. Instead, it This module does not define any management objects. Instead, it
assigns a set of OBJECT-IDENTITIES which may be used by other MIB assigns a set of OBJECT-IDENTITIES which may be used by other MIB
modules to identify specific IP Performance Metrics. modules to identify specific IP Performance Metrics.
Meaningful security considerations can only be written in the MIB Meaningful security considerations can only be written in the MIB
skipping to change at page 16, line 28 skipping to change at page 14, line 28
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC2678] Mahdavi, J. and V. Paxson, "IPPM Metrics for Measuring [RFC2678] Mahdavi, J. and V. Paxson, "IPPM Metrics for Measuring
Connectivity", RFC 2678, September 1999. Connectivity", RFC 2678, September 1999.
[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.
[RFC2680] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way [RFC2680] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way
Packet Loss Metric for IPPM", RFC 2680, September 1999. Packet Loss Metric for IPPM", RFC 2680, September 1999.
[RFC2681] Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip [RFC2681] Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip
skipping to change at page 17, line 15 skipping to change at page 15, line 10
[RFC3432] Raisanen, V., Grotefeld, G. and A. Morton, "Network [RFC3432] Raisanen, V., Grotefeld, G. and A. Morton, "Network
performance measurement with periodic streams", RFC 3432, performance measurement with periodic streams", RFC 3432,
November 2002. November 2002.
8.2 Informative References 8.2 Informative References
[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.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
Author's Address Author's Address
Stephan Emile Stephan Emile
France Telecom R & D France Telecom R & D
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/