Network Working Group E. Stephan Internet-Draft France Telecom R&D Category: Best Current Practice May 19, 2004 Expires: November 17, 2004 IPPM metrics registry draft-ietf-ippm-metrics-registry-06.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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. This Internet-Draft will expire on November 17, 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 in the future, both those standardized inside and outside the IETF. IANA has been assigned to administer this new registry. Stephan Expires November 17, 2004 [Page 1] Internet-Draft IPPM metrics registry May 2004 Table of Contents 1. The Internet-Standard Management Framework . . . . . . . . . . 3 2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. The IPPM Framework . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. IPPM metrics Registry framework . . . . . . . . . . . . . . . 4 6. Initial IPPM metrics registry creation . . . . . . . . . . . . 4 7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 5 7.1 Management rules . . . . . . . . . . . . . . . . . . . . . 5 7.1.1 Naming Conventions . . . . . . . . . . . . . . . . . . 5 7.1.2 Metrics defined by IETF . . . . . . . . . . . . . . . 5 7.1.3 Metrics defined in cooperation with other bodies . . . 5 7.1.4 Private Metrics registration . . . . . . . . . . . . . 6 7.2 Registration templates . . . . . . . . . . . . . . . . . . 6 7.2.1 IETF RFCs . . . . . . . . . . . . . . . . . . . . . . 6 7.2.2 Other Organizations . . . . . . . . . . . . . . . . . 7 7.2.3 Enterprises . . . . . . . . . . . . . . . . . . . . . 7 8. Initial IPPM registry definition . . . . . . . . . . . . . . . 7 9. Security Considerations . . . . . . . . . . . . . . . . . . . 15 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 10.1 Normative References . . . . . . . . . . . . . . . . . . . . 15 10.2 Informative References . . . . . . . . . . . . . . . . . . . 16 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17 Intellectual Property and Copyright Statements . . . . . . . . 18 Stephan Expires November 17, 2004 [Page 2] Internet-Draft IPPM metrics registry May 2004 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 Stephan Expires November 17, 2004 [Page 3] Internet-Draft IPPM metrics registry May 2004 standardized metrics; o As the intent of the IPPM WG is to cooperate with other appropriate standards bodies and other areas of IETF to promote consistent metrics, there is a need to permit registration of such metrics. 5. IPPM metrics Registry 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 determines the node which branch the metric is identified in: o Metrics defined by IETF are identified in the 'ietf' tree; o Metrics defined in cooperation with other organizations may be identified in the 'otherOrganizations' tree. o Vendors may register private metrics in the 'enterprises' 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. Initial IPPM metrics registry creation The initial registry identifies the metrics currently defined in the RFCs produced in the IPPM WG. By now, 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]; Stephan Expires November 17, 2004 [Page 4] Internet-Draft IPPM metrics registry May 2004 o IP Packet Delay Variation Metric, RFC 3393 [RFC3393]; o IPPM Metrics for periodic streams, RFC 3432 [RFC3432]; 7. IANA considerations This section describes the rules for the management of the registry by IANA. 7.1 Management rules 7.1.1 Naming Conventions The name of the metric in the registry must respect the SMIv2 rules for descriptors ([RFC2578], section 3.1) and should be easily readable. Consequently the following is applied to adapt the name used in the metric definition: o The name always starts with the prefix of the organization. o 'Type-P' prefix is removed. o '-' are removed; o The letter following a '-' is changed to upper case; o A node 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. 7.1.2 Metrics defined by IETF Such metrics are registered in the node ietf(1) after approval of the document by the IESG. The name always starts with the prefix 'ietf'. They are registered in the node ietf(1). They are numbered using the metrics definitions order in each memo. 7.1.3 Metrics defined in cooperation with other bodies After approval of the document by the IESG, IANA will assign the organization with a subtree under the branch otherOrganizations(2). The organization registers metrics under the branch Stephan Expires November 17, 2004 [Page 5] Internet-Draft IPPM metrics registry May 2004 otherOrganizations(2), in the corresponding subtree. The name of the metric always starts with the prefix of the organization. The prefix is the name of the subtree assigned to the organization. Nothing prevents these bodies from registering metrics in their own OBJECT INDENTIFIER trees. 7.1.4 Private Metrics 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 the IESG, an enterprise may register private metrics under the branch enterprises(3), in the subtree corresponding to its enterprise number. The name of the metric always starts with the prefix of the company. The enterprise is responsible for the assignment of the number if its subtree. Example: The enterprise Acme,which enterprise number is 100000, will register its metrics in the subtree ippmMetricsRegistry(x).enterprises(3).100000. 7.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 IETF RFCs For each metric, that section would have a statement aka: IANA has registed the following Metric in the IANA-IPPM-METRICS-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 nn } -- IANA assigns nn Stephan Expires November 17, 2004 [Page 6] Internet-Draft IPPM metrics registry May 2004 7.2.2 Other Organizations For each metric, that section would have a statement aka: IANA has registed the following Metric in the IANA-IPPM-METRICS-MIB: orgSomeNewMetricName OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Some-New_Metric-Name metric." REFERENCE "URL, section n." -- link to the org document. ::= { org nn } -- org assigns nn 7.2.3 Enterprises For each metric, that section would have a statement aka: Vendor has registed the following Metric: vendorSomeNewMetricName OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Some-New_Metric-Name metric." REFERENCE "URL, section n." -- link to the vendor document. ::= { vendorID nn } -- vendor assigns nn 8. Initial IPPM registry definition Stephan Expires November 17, 2004 [Page 7] Internet-Draft IPPM metrics registry May 2004 IANA-IPPM-METRICS-REGISTRY DEFINITIONS ::= BEGIN IMPORTS OBJECT-IDENTITY, MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI; ippmMetricsRegistry MODULE-IDENTITY REVISION "200405190000Z" -- May 19th, 2004 ORGANIZATION "IETF IPPM working Group" CONTACT-INFO " Emile STEPHAN France Telecom R&D 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 " DESCRIPTION "This memo defines a registry of the IPPM working group metrics. Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC yyyy; see the RFC itself for full legal notices." REVISION "200405190000Z" -- May 19th, 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 ::= { ippmMetricsRegistry 1 } otherOrganizations OBJECT IDENTIFIER ::= { ippmMetricsRegistry 2 } enterprises OBJECT IDENTIFIER ::= { ippmMetricsRegistry 3 } -- -- Registry of the metrics of the IPPM WG RFCs -- -- -- RFC 2678 " IPPM Metrics for Measuring Connectivity" -- ietfInstantUnidirConnectivity OBJECT-IDENTITY Stephan Expires November 17, 2004 [Page 8] Internet-Draft IPPM metrics registry May 2004 STATUS current DESCRIPTION "The identifier for the Type-P-Instantaneous-Unidirectional- Connectivity metric." REFERENCE "RFC2678, section 2." ::={rfc 1} ietfInstantBidirConnectivity OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-Instantaneous-Bidirectional- Connectivity metric." REFERENCE "RFC2678, section 3." ::={rfc 2} ietfIntervalUnidirConnectivity OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-Interval-Unidirectional- Connectivity metric." REFERENCE "RFC2678, section 4." ::= { rfc 3 } ietfIntervalBidirConnectivity OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-Interval-Bidirectional- Connectivity metric." REFERENCE "RFC2678, section 5." ::= { rfc 4 } ietfIntervalTemporalConnectivity 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" -- ietfOneWayDelay OBJECT-IDENTITY STATUS current Stephan Expires November 17, 2004 [Page 9] Internet-Draft IPPM metrics registry May 2004 DESCRIPTION "The identifier for the Type-P-One-way-Delay metric." REFERENCE "RFC2679, section 3." ::= { rfc 6 } ietfOneWayDelayPoissonStream OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-way-Delay-Poisson-Stream metric." REFERENCE "RFC2679, section 4." ::= { rfc 7 } ietfOneWayDelayPercentile OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-way-Delay-Percentile metric." REFERENCE "RFC2679, section 5.1." ::= { rfc 8 } ietfOneWayDelayMedian OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-way-Delay-Median metric." REFERENCE "RFC2679, section 5.2." ::= { rfc 9 } ietfOneWayDelayMinimum OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-way-Delay-Minimum metric." REFERENCE "RFC2679, section 5.3." ::= { rfc 10 } ietfOneWayDelayInversePercentile OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-way-Delay-Inverse- Percentile metric. " REFERENCE "RFC2679, section 5.4." ::= { rfc 11 } Stephan Expires November 17, 2004 [Page 10] Internet-Draft IPPM metrics registry May 2004 -- -- 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." REFERENCE "RFC2680, section 2." ::= { rfc 12 } ietfOneWayPktLossPoissonStream OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-way-Packet-Loss-Poisson- Stream metric." REFERENCE "RFC2680, section 3." ::= { rfc 13 } ietfOneWayPktLossAverage OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-way-Packet-Loss-Average metric." REFERENCE "RFC2680, section 4." ::= { rfc 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." REFERENCE " section 2 of the rfc2681." ::= { rfc 15 } ietfRoundTripDelayPoissonStream OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-Round-trip-Delay-Poisson -Stream metric." REFERENCE "RFC2681, section 4." ::= { rfc 16 } Stephan Expires November 17, 2004 [Page 11] Internet-Draft IPPM metrics registry May 2004 ietfRoundTripDelayPercentile OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-Round-trip-Delay-Percentile metric." REFERENCE "RFC2681, section 4.1." ::= { rfc 17 } ietfRoundTripDelayMedian OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-Round-trip-Delay-Median metric." REFERENCE "RFC2681, section 4.2." ::= { rfc 18 } ietfRoundTripDelayMinimum OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-Round-trip-Delay-Minimum metric." REFERENCE "RFC2681, section 4.3." ::= { rfc 19 } ietfRoundTripDelayInversePercentile 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" -- ietfOneWayLossDistanceStream OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-Way-Loss-Distance-Stream metric." REFERENCE " RFC3357, section 5.4.1." ::={ rfc 21} ietfOneWayLossPeriodStream OBJECT-IDENTITY Stephan Expires November 17, 2004 [Page 12] Internet-Draft IPPM metrics registry May 2004 STATUS current DESCRIPTION "The identifier for the Type-P-One-Way-Loss-Period-Stream metric." REFERENCE " RFC3357, section 5.4.2." ::={ rfc 22} ietfOneWayLossNoticeableRate OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-Way-Loss-Noticeable-Rate metric." REFERENCE " RFC3357, section 6.1." ::= { rfc 23 } ietfOneWayLossPeriodTotal OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-Way-Loss-Period-Total metric." REFERENCE " RFC3357, section 6.2." ::= { rfc 24 } ietfOneWayLossPeriodLengths OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-Way-Loss-Period-Lengths metric." REFERENCE " RFC3357, section 6.3." ::= { rfc 25 } ietfOneWayInterLossPeriodLengths 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) ietfOneWayIpdv OBJECT-IDENTITY STATUS current Stephan Expires November 17, 2004 [Page 13] Internet-Draft IPPM metrics registry May 2004 DESCRIPTION "The identifier for the Type-P-One-way-ipdv metric." REFERENCE " RFC3393, section 2." ::= { rfc 27 } ietfOneWayIpdvPoissonStream OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-way-ipdv-Poisson-stream metric." REFERENCE " RFC3393, section 3." ::= { rfc 28 } ietfOneWayIpdvPercentile OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-way-ipdv-percentile metric." REFERENCE " RFC3393, section 4.3." ::= { rfc 29 } ietfOneWayIpdvInversePercentile OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-way-ipdv-inverse -percentile metric." REFERENCE " RFC3393, section 4.4." ::= { rfc 30 } ietfOneWayIpdvJitter OBJECT-IDENTITY STATUS current DESCRIPTION "The identifier for the Type-P-One-way-ipdv-jitter metric." REFERENCE " RFC3393, section 4.5." ::= { rfc 31 } ietfOneWayPeakToPeakIpdv 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 } Stephan Expires November 17, 2004 [Page 14] Internet-Draft IPPM metrics registry May 2004 -- -- 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." REFERENCE " RFC3432, section 4." ::= { rfc 33 } END 9. 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. References 10.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. and S. Deering, "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification", RFC 2463, December 1998. [RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6 Specification", RFC 2473, December 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. Stephan Expires November 17, 2004 [Page 15] Internet-Draft IPPM metrics registry May 2004 [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 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. Stephan Expires November 17, 2004 [Page 16] Internet-Draft IPPM metrics registry May 2004 [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 Stephan Expires November 17, 2004 [Page 17] Internet-Draft IPPM metrics registry May 2004 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any intellectual property 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 does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice 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 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. 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 Stephan Expires November 17, 2004 [Page 18] Internet-Draft IPPM metrics registry May 2004 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Stephan Expires November 17, 2004 [Page 19]