Network Working Group                                         E. Stephan
Internet-Draft                                        France Telecom R&D
Category: Best Current Practice                             May 19, 2004
Expires: November 17, December 28, 2004

                         IPPM                                 June 29, 2004

             IP Performance Metrics (IPPM) metrics registry
                draft-ietf-ippm-metrics-registry-06.txt
                draft-ietf-ippm-metrics-registry-07.txt

Status of this Memo

   This document is an Internet-Draft

   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been disclosed,
   and is any of which I become aware will be disclosed, in full conformance accordance with
   all provisions of Section 10 of RFC2026.
   RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   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
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on November 17, December 28, 2004.

Copyright Notice

   Copyright (C) The Internet Society (2004).  All Rights Reserved.

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.

   This memo also defines the rules for adding new IP Performance
   Metrics that are defined in the future, both those standardized inside future.  There are branches for other
   standards bodies and outside the
   IETF. enterprises defined to encourage all IP
   performance metrics to be registered here.

   IANA has been assigned to administer this new registry.

Table of Contents

   1.  The Internet-Standard Management Framework . . . . . . . . . .  3
   2.  Terms  .  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  The IPPM  IP Performance Metrics Registry Framework  . . . . . . . . . . . . . . . . . . . . . .  3
   4.  Overview . . . . . . . . . . . . . . .  Initial IPPM Metrics Registry Creation . . . . . . . . . . . .  3  4
   5.  IPPM metrics Registry framework  . . . . . .  IANA Considerations  . . . . . . . . .  4
   6.  Initial IPPM metrics registry creation . . . . . . . . . . . .  4
   7.  IANA considerations  . . .
     5.1   Management rules . . . . . . . . . . . . . . . . . .  5
     7.1   Management rules . . .  4
       5.1.1   Naming Conventions . . . . . . . . . . . . . . . . . .  5
       7.1.1   Naming Conventions . . .
       5.1.2   Metrics Defined by IETF  . . . . . . . . . . . . . . .  5
       7.1.2
       5.1.3   Metrics defined by IETF Defined in Cooperation with Standards
               bodies or Fora . . . . . . . . . . . . . . .  5
       7.1.3   Metrics defined in cooperation with other bodies . . .  5
       7.1.4   Private Metrics registration . .  5
       5.1.4   Entreprise Metrics Registration  . . . . . . . . . . .  6
     7.2
     5.2   Registration templates . . . . . . . . . . . . . . . . . .  6
       7.2.1
       5.2.1   IETF RFCs  . . . . . . . . . . . . . . . . . . . . . .  6
       7.2.2   Other Organizations  . . .
       5.2.2   Standards bodies and Fora  . . . . . . . . . . . . . .  7
       7.2.3
       5.2.3   Enterprises  . . . . . . . . . . . . . . . . . . . . .  7
   8.
   6.  Initial IPPM registry definition . . . . . . . . . . . . . . .  7
   9.  8
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 15
   10. 16
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . 15
   10.1 . 16
   8.1   Normative References . . . . . . . . . . . . . . . . . . . . 15
   10.2 16
   8.2   Informative References . . . . . . . . . . . . . . . . . . . 16 17
       Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17
       Intellectual Property and Copyright Statements . . . . . . . . 18

1.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].  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].

2.  Terms

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, RFC 2119
   [RFC2119].

3.  The IPPM Framework

   The IPPM Framework consists in four major components:

   o  A general framework for defining performance metrics described in
      the Framework for IP Performance Metrics RFC2330 [RFC2330];

   o  A set of standardized metrics, which conform to this framework.

   o  Emerging metrics which are being specified in respect of this
      framework;

   o  The IPPM-REPORTING-MIB for reporting the results of the measures
      and for interfacing heterogeneous measurement systems with
      management entities.

4.  Overview

   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  Metrics identifiers are needed to allow measurement
      interoperability; As specification of new metrics is a continuous
      process, special care must be taken for the integration of future
      standardized metrics;

   o  As  Since the intent of the IPPM WG is to cooperate with other
      appropriate standards bodies and other areas of IETF (or fora) to promote consistent
      metrics, there a branch where other standards bodies can register their
      metrics is provided to encourage IP performance metrics to have
      OBJECT IDENTITIES rooted at a need common point;

   o  Similarly, a branch is provided for registered enterprises to permit registration of such
      register metrics.

5.  IPPM metrics

3.  IP Performance Metrics Registry framework Framework

   MIB modules need to be able to precisely reference IPPM Metrics.  The
   registry associates an OBJECT-IDENTITY with each metric.  As an
   example Type-P-One-way-Delay and Type-P-One-way-Delay-Poisson-Stream
   have different OBJECT IDENTITIES.

   The registry has 3 main branches.  The origin of the document
   defining the metrics determines the node which branch the metric is
   identified in:

   o  Metrics defined by IETF are identified in the 'ietf'
      'ianaIppmIetfMetrics' tree;

   o  Metrics defined in cooperation with other organizations standards bodies or fora may
      be identified in the 'otherOrganizations' 'ianaIppmForaMetrics' tree.

   o  Vendors may register private metrics in the 'enterprises'
      'ianaIppmEnterprisesMetrics' tree.

   This document defines an initial registry of the existing metrics and
   the rules to manage the registry.

   Documents defining metrics in the future will include in the IANA
   section the registration information to unambiguously identify these
   metrics.

6.

4.  Initial IPPM metrics registry creation Metrics Registry Creation

   The initial registry identifies the metrics currently defined in the
   RFCs produced in the IPPM WG. By now,  To date, the IPPM WG defined 33
   metrics related to 7 topics:

   o  IPPM Metrics for Measuring Connectivity, RFC 2678 [RFC2678];

   o  One-way Delay Metrics, RFC 2679  [RFC2679];

   o  One-way Packet Loss Metrics, RFC 2680 [RFC2680];

   o  Round-trip Delay Metrics, RFC 2681 [RFC2681];

   o  One-way Loss Pattern Sample Metrics, RFC 3357 [RFC3357];

   o  IP Packet Delay Variation Metric, RFC 3393 [RFC3393];

   o  IPPM Metrics for periodic streams, RFC 3432 [RFC3432];

7.

5.  IANA considerations Considerations

   This section describes the rules for the management of the registry
   by IANA.

7.1

5.1  Management rules

7.1.1

   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 ([RFC2578], defined in the section 3.1) and should 3.1 of [RFC2578]:

   o  Descriptors longer than 32 characters are not recommended;

   o  Initial character must be easily
   readable. Consequently the a lower-case letter;

   o  Hyphens are not allowed;

   The following is rules are applied to adapt allocate the name
   used in and the metric definition:
   identifier of a metric:

   o  The name always starts with the prefix name of the organization. organization;

   o  'Type-P' prefix is removed.

   o  '-'  OBJECT IDENTITIES for metrics are removed;

   o  The letter following a '-' is changed to upper case; sequentially numbered by IANA;

   o  A node OBJECT IDENTITY assigned to a metric is definitive and cannot be reused.
      reused;

   o  If a new version of a metric is produced then it is assigned with
      a new name and a new identifier.

7.1.2

5.1.2  Metrics defined Defined by IETF

   Such metrics are registered in the node ietf(1) after approval of the
   document by ianaIppmIetfMetrics(1).  The
   guidelines used for the IESG. existing metrics, and encouraged for new
   metrics, are

   o  The name always starts with the prefix 'ietf'. They are registered in
   the node ietf(1). They

   o  'Type-P' prefix is removed.

   o  '-' are numbered using the metrics definitions
   order in each memo.

7.1.3 removed;

   o  The letter following a '-' is changed to upper case;

5.1.3  Metrics defined Defined in cooperation Cooperation with other Standards bodies

   After approval of the document by the IESG, or Fora

   IANA will assign the
   organization already assigns enterprises with a subtree under the branch otherOrganizations(2).

   The organization 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
   otherOrganizations(2),
      ianaIppmForaMetrics(2), in the subtree corresponding subtree. to its
      enterprise number.

   o  The name of the metric always starts with (an abbreviation of) the prefix
      name of the organization. The prefix
   is

   For example, if the name of organisation ForumA has been assigned {
   enterprises 696 }, it will register its metrics in the subtree assigned to
   ianaIppmMetricsRegistry(x).ianaIppmForaMetrics(2).696.  The name of a
   metric starts with the organization. prefix 'ForumA'.

   Nothing prevents these bodies from registering metrics in their own
   OBJECT INDENTIFIER trees.

7.1.4  Private

5.1.4  Entreprise Metrics registration Registration

   IANA already assigns enterprises with unambiguous identifiers named
   enterprise numbers or vendorID.  See
   http://www.iana.org/numbers.html.

   After approval of the document by

   o  An enterprise without an entreprise number should apply for one;

   o  IANA registers the IESG, metrics of an enterprise may
   register private metrics under the branch enterprises(3),
      ianaIppmEnterprisesMetrics(3), in the subtree corresponding to its
      enterprise number.

   o  The name of the metric always starts with (an abbreviation of) the prefix
      name of the company.

   The enterprise is responsible for the assignment of the number

   For example, if its
   subtree.

   Example: The enterprise Acme,which enterprise number is 100000, Acme Networks has been assigned { enterprises 696 },
   it will register its metrics in the subtree
   ippmMetricsRegistry(x).enterprises(3).100000.

7.2
   ianaIppmMetricsRegistry(x).ianaIppmEnterprisesMetrics(3).696.  The
   name of a metric starts with the prefix 'Acme'.

5.2  Registration templates

   A document that creates new Metrics would have an IANA considerations
   section in which it would describe new metrics to register.

7.2.1

5.2.1  IETF RFCs

   For each metric, that section would have a statement aka:

      IANA has registed the following Metric metric in the IANA-IPPM-METRICS-MIB:
      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
          ::= { ietf ianaIppmIetfMetrics nn }     -- IANA assigns nn

7.2.2  Other Organizations

5.2.2  Standards bodies and Fora

   For each metric, that section would have a statement aka:

      IANA has registed the following Metric metric in the IANA-IPPM-METRICS-MIB:

   	orgSomeNewMetricName
      IANA-IPPM-METRICS-REGISTRY-MIB:

       foraNameSomeNewMetricName OBJECT-IDENTITY
          STATUS       current
          DESCRIPTION "The identifier for the Some-New_Metric-Name
              metric."
          REFERENCE   "URL,   "Specification title/revision/date, section n."    -- link to the org document.
          ::= { org foraEnterpriseNumber nn }           -- org IANA assigns nn

7.2.3

5.2.3  Enterprises

   For each metric, that section would have a statement aka:

   Vendor

      IANA has registed the following Metric:

   	vendorSomeNewMetricName metric in the
      IANA-IPPM-METRICS-REGISTRY-MIB:

       vendorNameSomeNewMetricName OBJECT-IDENTITY
          STATUS       current
          DESCRIPTION "The identifier for the Some-New_Metric-Name
              metric."
          REFERENCE   "URL,   "Specification title/revision/date, section n."    -- link to the vendor document.
         ::=         { vendorID vendorEnterpriseNumber nn }  -- vendor IANA assigns nn

8.

6.  Initial IPPM registry definition
   IANA-IPPM-METRICS-REGISTRY

   IANA-IPPM-METRICS-REGISTRY-MIB DEFINITIONS ::= BEGIN

   IMPORTS
       OBJECT-IDENTITY, MODULE-IDENTITY, mib-2
           FROM SNMPv2-SMI;

   ippmMetricsRegistry

   ianaIppmMetricsRegistry MODULE-IDENTITY
   REVISION      "200405190000Z"
   LAST-UPDATED "200406280000Z"    -- May 19th, June 28th, 2004
   ORGANIZATION       "IETF IPPM working Group" "IANA"
   CONTACT-INFO       "
   			Emile STEPHAN
   			France Telecom R&D "Internet Assigned Numbers Authority

            Postal: ICANN
                4676 Admiralty Way, Suite 330
                Marina del Rey, CA 90292

            Tel:    +1 33 2 96 05 36 10
   	E-mail: emile.stephan@francetelecom.com
   	Postal: 2, avenue Pierre Marzin
   			Lannion, FRANCE 22307

   	Send comments to ippm@ietf.org
   	Mailing list subscription info:
   	https://www1.ietf.org/mailman/listinfo/ippm " 310 823 9358
            E-Mail: iana@iana.org"

   DESCRIPTION

      "This memo module defines a registry registry for IP Performance (IPPM) 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
         in the section 3.1 of [RFC2578];

      *  Metrics defined by IETF are registed by IANA in the
         ianaIppmIetfMetrics subtree;

      *  Metrics defined by a standards bodies are registed by IANA
         under the node corresponding to the entreprise number of this
         organisation in the IPPM working group
   	metrics. ianaIppmForaMetrics subtree;

      *  Metrics defined by an enterprise are registed by IANA under the
         node corresponding to the entreprise number of this company in
         the ianaIppmEnterprisesMetrics subtree;

      The rules are fully described in the 'IANA considerations'
      section.

      Copyright (C) The Internet Society (2004). This  The initial version of
      this MIB module is part of was published in RFC yyyy; for full legal notices
      see the RFC itself for
   	full legal notices." or see:
      http://www.ietf.org/copyrights/ianamib.html.  "

      -- RFC Ed.: replace yyyy with actual RFC number & remove this note

   REVISION      "200405190000Z"      "200406280000Z"    -- May 19th, June 28th, 2004
   DESCRIPTION
       "Initial version of the IPPM metrics registry module.
        This version published as RFC yyyy."
   ::= { mib-2 XXX }  -- XXX to be assigned by IANA

   ietf               OBJECT IDENTIFIER

   ianaIppmIetfMetrics OBJECT-IDENTITY
       STATUS       current
       DESCRIPTION
           "Registration point for IP Performance (IPPM) Metrics
            defined by the IETF."
       ::= { ippmMetricsRegistry ianaIppmMetricsRegistry 1 }
   otherOrganizations OBJECT IDENTIFIER

   ianaIppmForaMetrics OBJECT-IDENTITY
       STATUS       current
       DESCRIPTION
           "Registration point for IP Performance Metrics
            defined by other (i.e., non-IETF) organizations."
       ::= { ippmMetricsRegistry ianaIppmMetricsRegistry 2 }

   ianaIppmEnterprisesMetrics OBJECT-IDENTITY
       STATUS       current
       DESCRIPTION
           "Registration point for IP Performance Metrics
            defined by enterprises        OBJECT IDENTIFIER or vendors."
       ::= { ippmMetricsRegistry ianaIppmMetricsRegistry 3 }

     --
     -- Registry of the metrics of the IPPM WG RFCs
     --
     --
     -- RFC 2678 " IPPM Metrics for Measuring Connectivity"
     --

   ietfInstantUnidirConnectivity OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-Instantaneous-Unidirectional-
           Connectivity metric."
           "Type-P-Instantaneous-Unidirectional-Connectivity"
       REFERENCE "RFC2678, section 2."
       ::={rfc
       ::= { ianaIppmIetfMetrics 1}

   ietfInstantBidirConnectivity OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-Instantaneous-Bidirectional-
           Connectivity metric."
           "Type-P-Instantaneous-Bidirectional-Connectivity"
       REFERENCE "RFC2678, section 3."
       ::={rfc
       ::= { ianaIppmIetfMetrics 2}

   ietfIntervalUnidirConnectivity OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-Interval-Unidirectional-
           Connectivity metric."
           "Type-P-Interval-Unidirectional-Connectivity"
       REFERENCE "RFC2678, section 4."
       ::= { rfc ianaIppmIetfMetrics 3 }

   ietfIntervalBidirConnectivity OBJECT-IDENTITY
       STATUS current
       DESCRIPTION
           "The identifier for the Type-P-Interval-Bidirectional-
           Connectivity metric."
           "Type-P-Interval-Bidirectional-Connectivity"
       REFERENCE "RFC2678, section 5."
       ::= { rfc ianaIppmIetfMetrics 4 }

   ietfIntervalTemporalConnectivity OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P1-P2-Interval-Temporal-
           Connectivity metric."
           "Type-P1-P2-Interval-Temporal-Connectivity"
       REFERENCE "RFC2678, section 6."
       ::= { rfc ianaIppmIetfMetrics 5 }

   --
   -- RFC 2679 "A One-way Delay Metric for IPPM"
   --

   ietfOneWayDelay OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-Delay metric."
           "Type-P-One-way-Delay"
       REFERENCE "RFC2679, section 3."
       ::= { rfc ianaIppmIetfMetrics 6 }

   ietfOneWayDelayPoissonStream OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-Delay-Poisson-Stream
           metric."
           "Type-P-One-way-Delay-Poisson-Stream"
       REFERENCE "RFC2679, section 4."
       ::= { rfc ianaIppmIetfMetrics 7 }

   ietfOneWayDelayPercentile OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-Delay-Percentile
           metric."
           "Type-P-One-way-Delay-Percentile"
       REFERENCE "RFC2679, section 5.1."
       ::= { rfc ianaIppmIetfMetrics 8 }

   ietfOneWayDelayMedian OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-Delay-Median metric."
           "Type-P-One-way-Delay-Median"
       REFERENCE "RFC2679, section 5.2."
       ::= { rfc ianaIppmIetfMetrics 9 }

   ietfOneWayDelayMinimum OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-Delay-Minimum metric."
           "Type-P-One-way-Delay-Minimum"
       REFERENCE "RFC2679, section 5.3."
       ::= { rfc ianaIppmIetfMetrics 10 }

   ietfOneWayDelayInversePercentile OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-Delay-Inverse-
           Percentile metric. "
           "Type-P-One-way-Delay-Inverse-Percentile"
       REFERENCE "RFC2679, section 5.4."
       ::= { rfc ianaIppmIetfMetrics 11 }
   --
   -- RFC 2680  "One Way Packet Loss Metric for IPPM"
   --

   ietfOneWayPktLoss OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-Packet-Loss metric."
           "Type-P-One-way-Packet-Loss"
       REFERENCE "RFC2680, section 2."
       ::= { rfc ianaIppmIetfMetrics 12 }

   ietfOneWayPktLossPoissonStream OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-Packet-Loss-Poisson-
           Stream metric."
           "Type-P-One-way-Packet-Loss-Poisson-Stream"
       REFERENCE "RFC2680, section 3."
       ::= { rfc ianaIppmIetfMetrics 13 }

   ietfOneWayPktLossAverage OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-Packet-Loss-Average
           metric."
           "Type-P-One-way-Packet-Loss-Average"
       REFERENCE "RFC2680, section 4."
       ::= { rfc ianaIppmIetfMetrics 14 }

   -- TODO remnae as V5 in v5 dir
   -- RFC2681 "A Round-trip Delay Metric for IPPM"
   --

   ietfRoundTripDelay OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-Round-trip-Delay metric."
           "Type-P-Round-trip-Delay"
       REFERENCE " section 2 of the rfc2681."
       ::= { rfc ianaIppmIetfMetrics 15 }

   ietfRoundTripDelayPoissonStream OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-Round-trip-Delay-Poisson
           -Stream metric."
           "Type-P-Round-trip-Delay-Poisson-Stream"
       REFERENCE "RFC2681, section 4."
       ::= { rfc ianaIppmIetfMetrics 16 }

   ietfRoundTripDelayPercentile OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-Round-trip-Delay-Percentile
           metric."
           "Type-P-Round-trip-Delay-Percentile"
       REFERENCE "RFC2681, section 4.1."
       ::= { rfc ianaIppmIetfMetrics 17 }

   ietfRoundTripDelayMedian OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
   		"The identifier for the Type-P-Round-trip-Delay-Median
   		 metric."
           "Type-P-Round-trip-Delay-Median"
       REFERENCE "RFC2681, section 4.2."
       ::= { rfc ianaIppmIetfMetrics 18 }

   ietfRoundTripDelayMinimum OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-Round-trip-Delay-Minimum
           metric."
           "Type-P-Round-trip-Delay-Minimum"
       REFERENCE "RFC2681, section 4.3."
       ::= { rfc ianaIppmIetfMetrics 19 }

   ietfRoundTripDelayInversePercentile

   ietfRoundTripDelayInvPercentile OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-Round-trip-Inverse-Percentile
           metric."
           "Type-P-Round-trip-Inverse-Percentile"
       REFERENCE "RFC2681, section 4.4."
       ::= { rfc ianaIppmIetfMetrics 20 }

   --
   -- RFC3357: "One-way Loss Pattern Sample Metrics"
   --

   ietfOneWayLossDistanceStream OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-Way-Loss-Distance-Stream
           metric."
           "Type-P-One-Way-Loss-Distance-Stream"
       REFERENCE " RFC3357, section 5.4.1."
       ::={ rfc ianaIppmIetfMetrics 21}

   ietfOneWayLossPeriodStream OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-Way-Loss-Period-Stream
           metric."
           "Type-P-One-Way-Loss-Period-Stream"
       REFERENCE " RFC3357, section 5.4.2."
       ::={ rfc ianaIppmIetfMetrics 22}

   ietfOneWayLossNoticeableRate OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-Way-Loss-Noticeable-Rate
           metric."
           "Type-P-One-Way-Loss-Noticeable-Rate"
       REFERENCE " RFC3357, section 6.1."
       ::= { rfc ianaIppmIetfMetrics 23 }

   ietfOneWayLossPeriodTotal OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-Way-Loss-Period-Total
           metric."
           "Type-P-One-Way-Loss-Period-Total"
       REFERENCE " RFC3357, section 6.2."
       ::= { rfc ianaIppmIetfMetrics 24 }

   ietfOneWayLossPeriodLengths OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-Way-Loss-Period-Lengths
           metric."
           "Type-P-One-Way-Loss-Period-Lengths"
       REFERENCE " RFC3357, section 6.3."
       ::= { rfc ianaIppmIetfMetrics 25 }

   ietfOneWayInterLossPeriodLengths OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-Way-Inter-Loss-Period-
           Lengths metric."
           "Type-P-One-Way-Inter-Loss-Period-Lengths"
       REFERENCE " RFC3357, section 6.4."
       ::= { rfc ianaIppmIetfMetrics 26 }

   --
   -- RFC3393:
   -- IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)

   ietfOneWayIpdv OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-ipdv metric."
           "Type-P-One-way-ipdv"
       REFERENCE " RFC3393, section 2."
       ::= { rfc ianaIppmIetfMetrics 27 }

   ietfOneWayIpdvPoissonStream OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-ipdv-Poisson-stream
           metric."
           "Type-P-One-way-ipdv-Poisson-stream"
       REFERENCE " RFC3393, section 3."
       ::= { rfc ianaIppmIetfMetrics 28 }
   ietfOneWayIpdvPercentile OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
         "The identifier for the Type-P-One-way-ipdv-percentile metric."
         "Type-P-One-way-ipdv-percentile"
       REFERENCE " RFC3393, section 4.3."
       ::= { rfc ianaIppmIetfMetrics 29 }

   ietfOneWayIpdvInversePercentile OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-ipdv-inverse
           -percentile metric."
           "Type-P-One-way-ipdv-inverse-percentile"
       REFERENCE " RFC3393, section 4.4."
       ::= { rfc ianaIppmIetfMetrics 30 }

   ietfOneWayIpdvJitter OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-ipdv-jitter metric."
           "Type-P-One-way-ipdv-jitter"
       REFERENCE " RFC3393, section 4.5."
       ::= { rfc ianaIppmIetfMetrics 31 }

   ietfOneWayPeakToPeakIpdv OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-peak-to-peak-ipdv
           metric."
           "Type-P-One-way-peak-to-peak-ipdv"
       REFERENCE " RFC3393, section 4.6."
       ::= { rfc ianaIppmIetfMetrics 32 }

   --
   -- RFC3432: "Network performance measurement with periodic streams"
   --

   ietfOneWayDelayPeriodicStream OBJECT-IDENTITY
       STATUS     current
       DESCRIPTION
           "The identifier for the Type-P-One-way-Delay-Periodic-Stream
           metric."
           "Type-P-One-way-Delay-Periodic-Stream"
       REFERENCE " RFC3432, section 4."
       ::= { rfc ianaIppmIetfMetrics 33 }

   END

9.

7.  Security Considerations

   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.

   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.

10.

8.  References

10.1

8.1  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2460]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
              (IPv6) Specification", RFC 2460, December 1998.

   [RFC2463]  Conta, A.

   [RFC2434]  Narten, T. and S. Deering, "Internet Control Message
              Protocol (ICMPv6) H. Alvestrand, "Guidelines for the Internet Protocol Version 6
              (IPv6) Specification", RFC 2463, December 1998.

   [RFC2473]  Conta, A. and S. Deering, "Generic Packet Tunneling Writing an
              IANA Considerations Section in
              IPv6 Specification", RFCs", BCP 26, RFC 2473, December 2434,
              October 1998.

   [RFC2578]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
              McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of
              Management Information Version 2 (SMIv2)", STD 58, RFC
              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
              Connectivity", RFC 2678, September 1999.

   [RFC2679]  Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way
              Delay Metric for IPPM", RFC 2679, September 1999.

   [RFC2680]  Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way
              Packet Loss Metric for IPPM", RFC 2680, September 1999.

   [RFC2681]  Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip
              Delay Metric for IPPM", RFC 2681, September 1999.

   [RFC2895]  Bierman, A., Bucci, C. and R. Iddon, "Remote Network
              Monitoring MIB Protocol Identifier Reference", RFC 2895,
              August 2000.

   [RFC3032]  Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
              Farinacci, D., Li, T. and A. Conta, "MPLS Label Stack
              Encoding", RFC 3032, January 2001.

   [RFC3357]  Koodli, R. and R. Ravikanth, "One-way Loss Pattern Sample
              Metrics", RFC 3357, August 2002.

   [RFC3393]  Demichelis, C. and P. Chimento, "IP Packet Delay Variation
              Metric for IP Performance Metrics (IPPM)", RFC 3393,
              November 2002.

   [RFC3432]  Raisanen, V., Grotefeld, G. and A. Morton, "Network
              performance measurement with periodic streams", RFC 3432,
              November 2002.

10.2

8.2  Informative References

   [RFC2026]  Bradner, S., "The Internet Standards Process -- Revision
              3", BCP 9, RFC 2026, October 1996.

   [RFC2330]  Paxson, V., Almes, G., Mahdavi, J. and M. Mathis,
              "Framework for IP Performance Metrics", RFC 2330, May
              1998.

   [RFC2896]  Bierman, A., Bucci, C. and R. Iddon, "Remote Network
              Monitoring MIB Protocol Identifier Macros", RFC 2896,
              August 2000.

   [RFC3410]  Case, J., Mundy, R., Partain, D. and B. Stewart,
              "Introduction and Applicability Statements for
              Internet-Standard Management Framework", RFC 3410,
              December 2002.

Author's Address

   Stephan Emile
   France Telecom R & D
   2 avenue Pierre Marzin
   Lannion,   F-22307

   Fax:   +33 2 96 05 18 52
   EMail: emile.stephan@francetelecom.com

Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property
   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; neither nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation RFC documents can be
   found in BCP-11. BCP 78 and BCP 79.

   Copies of
   claims of rights IPR disclosures made available for publication 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 implementors implementers or users of this
   specification can be obtained from the IETF Secretariat. on-line IPR repository at
   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 which that may cover technology that may be required to practice implement
   this standard.  Please address the information to the IETF Executive
   Director.

Full Copyright Statement

   Copyright (C) The Internet Society (2004). All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works. However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose at
   ietf-ipr@ietf.org.

Disclaimer of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assignees. Validity

   This document and the information contained herein is 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 DISCLAIMS 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.

Copyright Statement

   Copyright (C) The Internet Society (2004).  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.

Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.