[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 RFC 4148

   Network Working Group                                         E. Stephan
   Internet Draft                                        France Telecom R&D
   Document: draft-ietf-ippm-metrics-registry-02.txt        March 1st, 2002
   
   
   
                                                         IPPM metrics registry
   
   Status of this Memo
   
   
          This document is an Internet-Draft and is in full conformance with
          all provisions of Section 10 of RFC2026 [1].
   
          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.
   
          The list of Internet-Draft Shadow Directories can be accessed at
          http://www.ietf.org/shadow.html.
   
   
   Abstract
   
          This memo defines a registry of the IPPM working group metrics. It
          provides an OBJECT IDENTIFIER to each metric currently standardized
          by the IPPM WG. It defines the rules for the identification of the
          metrics standardized in the future.
   
   Table of Contents
   
          1.      Introduction................................................2
          2.      The IPPM Framework..........................................2
          3.      Overview....................................................2
          4.      IPPM metrics Registry framework.............................2
          4.1.    Metrics registry template...................................3
          4.2.    Initial IPPM metrics registry...............................4
          4.3.    IPPM registry management....................................4
          4.4.    Identification of metric from other organization............4
          5.      Initial IPPM registry.......................................4
          6.      Change since release 00....................................11
          7.      Change since release 01....................................11
          8.      References.................................................11
   
   Stephan          Informational - Expires December 2002         [Page 1]


   Internet Draft           IPPM metrics registry                June 2002
   
   
          9.      Author's Addresses.........................................12
   
   
   1. Introduction
   
          This memo defines a registry of the IPPM working group metrics. It
          provides an OBJECT IDENTIFIER to each metric currently standardized
          by the IPPM WG. It defines the rules for the identification of the
          metrics standardized in the future.
   
   2. The IPPM Framework
   
          The IPPM Framework consists in four major components:
   
                   + A general framework for defining performance metrics,
                   described  in the Framework for IP Performance Metrics, RFC
                   2330;
   
                   + A set of standardized metrics, which conform to this
                   framework. The IPPM Metrics for Measuring Connectivity, RFC 2678
                   [2]. The One-way Delay Metric for IPPM, RFC 2679 [3]. The One-
                   way Packet Loss Metric for IPPM, RFC 2680 [4]. The Round-trip
                   Delay Metric for IPPM, RFC 2681 [5];
   
                   + Emerging metrics which are being specified in respect of this
                   framework;
   
                   + The IPPM-REPORTING-MIB for reporting the results of the
                   measures and for interfacing heterogeneous measurement systems
                   with management entities.
   
   
   3. Overview
   
          This memo defines a registry of the current metrics and a framework
          for the integration of the future metrics for the following reasons:
   
                   + to permit metrics to be clearly referenced by MIBs or other
                   data models;
   
                   + Metrics identifiers are needed to allow measurement
                   interoperability;
   
                   + Specification of new metrics is a continuous process, special
                   care must be taken for the integration of the future
                   standardized metrics.
   
   4. IPPM metrics Registry framework
   
          MIBs need OBJECT INDENTIFIER to refer precisely to the standardized
          metrics. The registry associates an OBJECT IDENTIFIER to each metric.
   
   Stephan          Informational - Expires December 2002         [Page 2]


   Internet Draft           IPPM metrics registry                June 2002
   
   
          As an example oneWayDelay and oneWayDelayPoissonStream have different
          identifiers.
   
          The registry has 2 root branches. The category of the document
          determines the node the branch the metric is identified in:
   
                 + Metrics defined in a RFC are identified in the 'rfc' tree;
                 + Metrics defined elsewhere may be identified in the 'other' tree.
   
          The name of the metric has to respect ASN.1 constraints. The name has
          to start with a lower case. The letter - is forbidden (more or less)
          in the name. In a way to preserve the readability of the metric name
          the letters following a - are forced to upper case.
   
          Sometime the name of the metric starts with 'Type-P'. It depends on
          the document not the semantic of the metric. In the registry it is
          removed from the name of the metric to reduce the length of the name
          and to uniforms the metrics names.
   
          Each metrics specification will include a section describing its
          metrics identifiers.
   
   
   4.1. Metrics registry template
   
          Each memo includes a registry where are identified the metrics. The
          name of the section where is defined the registry terminate by
          'metrics registry'. The registry is defined using a MODULE-IDENTITY
          macro. Each metric is identify in the registry using a OBJECT-
          IDENTITY macro. The identification defines the metric name, status,
          reference and OBJECT IDENTIFIER.
   
   
          IPPM-XXX-METRICS-REGISTRY DEFINITIONS ::= BEGIN
   
                  XXXMetricsRegistry MODULE-IDENTITY
                  DESCRIPTION
                   " This memo defines a registry for XXX metrics."
                  ::= { xxx N }
   
                  xxxMetric1Name OBJECT-IDENTITY
                         DESCRIPTION
                                 "The identifier for the metric1."
                         REFERENCE
                                 "xxx, section x."
                   ::= { rfc  i }
   
                  xxxMetric2Name OBJECT-IDENTITY
                  DESCRIPTION
                          "The identifier for the metric1."
                  REFERENCE
   
   Stephan          Informational - Expires December 2002         [Page 3]


   Internet Draft           IPPM metrics registry                June 2002
   
   
                          "xxx, section y."
                  ::= { rfc  j }
   
          END
   
   
   
   
   
   4.2. Initial IPPM metrics registry
   
   
          Metrics specified in a RFC of the WG IPPM are registered in the node
          rfc(1). They are numbered using the RFC order and the metrics
          definitions order in each memo. The value assigned to a metric is
          definitive and cannot be reused.
   
          These rules are applied to create the first IPPM the registry. The
          metrics already standardized are registered in the section named
          'IPPM metrics registry' of this memo.
   
   
   4.3. IPPM registry management
   
          Usually, metrics are implemented during the specification process. At
          this step, a metric is not identified as an IPPM metric. There is a
          need to provide temporary metric identifiers to facilitate software
          integration and to permit interoperability measurement among
          different implementations. Otherwise the interoperability will be
          extremely limited du to the fact that implementers will choose
          arbitrary values to identify the new metrics.
   
          When the draft is considered mature, that is when all the metrics are
          defined and when they names are chosen:
   
                  The authors will insert a registry in the section 'Standard
                  metrics registry' of their document. A registry template is
                  proposed above.
   
                  The chairs of the IPPM WG provide metrics identifiers from the
                  rfc(1) node of the registry.
   
   4.4. Identification of metric from other organization
   
          Metrics defined by other organization may be registered in the node
          other(2).
   
   5. Initial IPPM registry
   
   IPPM-METRICS-REGISTRY DEFINITIONS ::= BEGIN
   
   
   Stephan          Informational - Expires December 2002         [Page 4]


   Internet Draft           IPPM metrics registry                June 2002
   
   
   IMPORTS
          OBJECT-IDENTITY,
          experimental,
          MODULE-IDENTITY
                  FROM SNMPv2-SMI;
   
   ippmMetricsRegistry MODULE-IDENTITY
          LAST-UPDATED "200303011100Z"    -- March 1st, 2003
          ORGANIZATION "IPPM working Group"
          CONTACT-INFO "ippm@advanced.org"
          DESCRIPTION
                  " This memo defines a portion of the Management Information Base
                  (MIB) for use with network management protocols in TCP/IP-based
                  internets. In particular, it defines a registry of the IPPM
                  working group metrics."
          REVISION      "200303011100Z"
          DESCRIPTION
                  "Registration rules simplified: see section change since 01."
          REVISION      "200206241100Z"
          DESCRIPTION
                  "Each metric identifier is defined in a OBJECT IDENTITY macro."
          ::= { experimental 10002 }
   
          rfc          OBJECT IDENTIFIER       ::= { ippmMetricsRegistry 1 }
          other        OBJECT IDENTIFIER       ::= { ippmMetricsRegistry 2 }
   
          --
          -- Registry of the metrics of the IPPM WG RFCs
          --
   
          --
          -- RFC 2678 " IPPM Metrics for Measuring Connectivity"
          --
   
          instantUnidirectionConnectivity OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-Instantaneous-Unidirectional-
          Connectivity metric."
                   REFERENCE "RFC2678, section 2."
                   ::={rfc 1}
   
          instantBidirectionConnectivity OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-Instantaneous-Bidirectional-
          Connectivity metric."
                   REFERENCE "RFC2678, section 3."
                        ::={rfc 2}
   
          intervalUnidirectionConnectivity OBJECT-IDENTITY
   
   Stephan          Informational - Expires December 2002         [Page 5]


   Internet Draft           IPPM metrics registry                June 2002
   
   
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-Interval-Unidirectional-
          Connectivity metric."
                   REFERENCE "RFC2678, section 4."
                        ::= { rfc 3 }
   
          intervalBidirectionConnectivity OBJECT-IDENTITY
                   STATUS current
                   DESCRIPTION
                   "The identifier for the Type-P-Interval-Bidirectional-
          Connectivity metric."
                   REFERENCE "RFC2678, section 5."
                        ::= { rfc  4 }
   
          intervalTemporalConnectivity OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P1-P2-Interval-Temporal-
          Connectivity metric. "
                   REFERENCE "RFC2678, section 6."
                        ::= { rfc  5 }
   
          --
          -- RFC 2679 "A One-way Delay Metric for IPPM"
          --
   
          oneWayDelay OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-Delay metric. "
                   REFERENCE "RFC2679, section 3."
                        ::= { rfc  6 }
   
          oneWayDelayPoissonStream OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-Delay-Poisson-Stream
          metric. "
                   REFERENCE "RFC2679, section 4"
                        ::= { rfc  7 }
   
          oneWayDelayPercentile OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-Delay-Percentile metric."
                   REFERENCE "RFC2679, section 5.1."
                        ::= { rfc  8 }
   
          oneWayDelayMedian OBJECT-IDENTITY
                   STATUS  current
   
   Stephan          Informational - Expires December 2002         [Page 6]


   Internet Draft           IPPM metrics registry                June 2002
   
   
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-Delay-Median metric."
                   REFERENCE "RFC2679, section 5.2."
                        ::= { rfc  9 }
   
          oneWayDelayMinimum OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-Delay-Minimum metric. "
                   REFERENCE "RFC2679, section 5.3."
                        ::= { rfc 10 }
   
          oneWayDelayInversePercentile OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-Delay-Inverse-Percentile
          metric. "
                   REFERENCE "RFC2679, section 5.4."
                        ::= { rfc 11 }
   
          --
          -- RFC 2680  "One Way Packet Loss Metric for IPPM"
          --
   
          oneWayPacketLoss OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-Packet-Loss metric."
                   REFERENCE "RFC2680, section 2."
                        ::= { rfc 12 }
   
          oneWayPacketLossPoissonStream OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-Packet-Loss-Poisson-
          Stream metric."
                   REFERENCE "RFC2680, section 3."
                        ::= { rfc 13 }
   
          oneWayPacketLossAverage OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-Packet-Loss-Average
          metric."
                   REFERENCE "RFC2680, section 4."
                        ::= { rfc 14 }
   
          --
          -- RFC2681 "A Round-trip Delay Metric for IPPM"
          --
   
   
   Stephan          Informational - Expires December 2002         [Page 7]


   Internet Draft           IPPM metrics registry                June 2002
   
   
          roundtripDelay OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-Round-trip-Delay metric."
                   REFERENCE " section 2 of the rfc2681."
                        ::= { rfc 15 }
   
          roundtripDelayPoissonStream OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-Round-trip-Delay-Poisson-Stream
          metric."
                   REFERENCE "RFC2681, section 4."
                        ::= { rfc 16 }
   
          roundtripDelayPercentile OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-Round-trip-Delay-Percentile
          metric."
                   REFERENCE "RFC2681, section 4.1."
                        ::= { rfc 17 }
   
          roundtripDelayMedian OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-Round-trip-Delay-Median metric."
                   REFERENCE "RFC2681, section 4.2."
                        ::= { rfc 18 }
   
          roundtripDelayMinimum OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-Round-trip-Delay-Minimum metric."
                   REFERENCE "RFC2681, section 4.3."
                        ::= { rfc 19 }
   
          roundtripDelayInversePercentile OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-Round-trip-Inverse-Percentile
          metric."
                   REFERENCE "RFC2681, section 4.4."
                        ::= { rfc 20 }
   
          --
          -- RFC3357: "One-way Loss Pattern Sample Metrics"
          --
   
          oneWayLossDistanceStream OBJECT-IDENTITY
                   STATUS  current
   
   Stephan          Informational - Expires December 2002         [Page 8]


   Internet Draft           IPPM metrics registry                June 2002
   
   
                   DESCRIPTION
                   "The identifier for the Type-P-One-Way-Loss-Distance-Stream
          metric."
                   REFERENCE " RFC3357, section 5.4.1."
                   ::={ rfc 21}
   
          oneWayLossPeriodStream OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-Way-Loss-Period-Stream
          metric."
                   REFERENCE " RFC3357, section 5.4.2."
                        ::={ rfc 22}
   
          oneWayLossNoticeableRate OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-Way-Loss-Noticeable-Rate
          metric."
                   REFERENCE " RFC3357, section 6.1."
                        ::= { rfc 23 }
   
          oneWayLossPeriodTotal OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-Way-Loss-Period-Total
          metric."
                   REFERENCE " RFC3357, section 6.2."
                        ::= { rfc 24 }
   
          oneWayLossPeriodLengths OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-Way-Loss-Period-Lengths
          metric."
                   REFERENCE " RFC3357, section 6.3."
                        ::= { rfc  25 }
   
          oneWayInterLossPeriodLengths OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-Way-Inter-Loss-Period-Lengths
          metric."
                   REFERENCE " RFC3357, section 6.4."
                        ::= { rfc 26 }
   
   
          --
          -- RFC3393: "IP Packet Delay Variation Metric for IP Performance
          Metrics (IPPM)"
          --
   
   Stephan          Informational - Expires December 2002         [Page 9]


   Internet Draft           IPPM metrics registry                June 2002
   
   
   
          oneWayIpdv OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-ipdv metric."
                   REFERENCE " RFC3393, section 2."
                        ::= { rfc 27 }
   
          oneWayIpdvPoissonStream OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-ipdv-Poisson-stream
          metric."
                   REFERENCE " RFC3393, section 3."
                        ::= { rfc 28 }
   
          oneWayIpdvPercentile OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-ipdv-percentile metric."
                   REFERENCE " RFC3393, section 4.3."
                        ::= { rfc 29 }
   
          oneWayIpdvInversePercentile OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-ipdv-inverse-percentile
          metric."
                   REFERENCE " RFC3393, section 4.4."
                        ::= { rfc 30 }
   
   
          oneWayIpdvJitter OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-ipdv-jitter metric."
                   REFERENCE " RFC3393, section 4.5."
                        ::= { rfc 31 }
   
          oneWayPeakToPeakIpdv OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-peak-to-peak-ipdv
          metric."
                   REFERENCE " RFC3393, section 4.6."
                        ::= { rfc 32 }
   
          --
          -- RFC3432: "Network performance measurement with periodic streams"
          --
   
   
   Stephan          Informational - Expires December 2002        [Page 10]


   Internet Draft           IPPM metrics registry                June 2002
   
   
          oneWayDelayPeriodicStream OBJECT-IDENTITY
                   STATUS  current
                   DESCRIPTION
                   "The identifier for the Type-P-One-way-Delay-Periodic-Stream
          metric."
                   REFERENCE " RFC3432, section 4."
                        ::= { rfc 33 }
   
   
          END
   
   
   6. Change since release 00
   
          Macro OBJECT-IDENTITY used to identify the metrics
   
   7. Change since release 01
   
          + Registrations rules simplified;
   
          + Draft sub tree removed;
   
          + Loss pattern metrics of the RFC3357 added to the registry.
   
          + ipdv metrics of the RFC3393 added to the registry.
   
          + Periodic streams metrics of the RFC3432 added to the registry.
   
   
          56th IETF open issues:
                  should metrics OID be 8 bytes length ? Y/N
                  -- should be ::= { ippm 1 }
                  -- with ippm OBJECT IDENTIFIER ::= { mgmt xxx }
                  -- to have metrics OID to be 8 bytes length.
                  -- 1.3.6.1.2.ippm.ippmMetricRegistry.rfc.oneWayDelay
   
   
   8. References
   
          [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP
                 9, RFC 2026, October 1996.
   
          [2] Mahdavi J. and V. Paxson, "IPPM Metrics for Measuring
                 Connectivity", RFC 2678, September 1999.
   
          [3] Almes, G.,  Kalidindi, S.  and M. Zekauskas, "A One-way Delay
                 Metric for IPPM", RFC 2679, September 1999.
   
   
   
   
   
   Stephan          Informational - Expires December 2002        [Page 11]


   Internet Draft           IPPM metrics registry                June 2002
   
   
   
          [4] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Packet
                 Loss Metric for IPPM", RFC 2680, September 1999.
   
          [5]Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip Delay
                 Metric for IPPM.", RFC 2681, September 1999.
   
   
   
   9. Author's Addresses
   
          Emile STEPHAN
          France Telecom R & D
          2 avenue Pierre Marzin
          F-22307 Lannion cedex
          Phone: (+ 33) 2 96 05 11 11
          Email: emile.stephan@francetelecom.com
   
   
   Full Copyright Statement
   
          "Copyright (C) The Internet Society (2001). 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 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 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 assigns.
   
          This document and the information contained herein is provided on an
          "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
          TASK FORCE DISCLAIMS 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.
   
   
   
   
   
   
   Stephan          Informational - Expires December 2002        [Page 12]
   

Html markup produced by rfcmarkup 1.129b, available from https://tools.ietf.org/tools/rfcmarkup/