draft-ietf-ippm-metrics-registry-06.txt   draft-ietf-ippm-metrics-registry-07.txt 
Network Working Group E. Stephan Network Working Group E. Stephan
Internet-Draft France Telecom R&D Internet-Draft France Telecom R&D
Category: Best Current Practice May 19, 2004 Expires: December 28, 2004 June 29, 2004
Expires: November 17, 2004
IPPM metrics registry IP Performance Metrics (IPPM) metrics registry
draft-ietf-ippm-metrics-registry-06.txt draft-ietf-ippm-metrics-registry-07.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC2026. 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
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 other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 http:// The list of current Internet-Drafts can be accessed at
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 November 17, 2004. This Internet-Draft will expire on December 28, 2004.
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 in the future, both those standardized inside and outside the Metrics that are defined in the future. There are branches for other
IETF. standards bodies and enterprises defined to encourage all IP
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. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The IPPM Framework . . . . . . . . . . . . . . . . . . . . . . 3 3. IP Performance Metrics Registry Framework . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Initial IPPM Metrics Registry Creation . . . . . . . . . . . . 4
5. IPPM metrics Registry framework . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Initial IPPM metrics registry creation . . . . . . . . . . . . 4 5.1 Management rules . . . . . . . . . . . . . . . . . . . . . 4
7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 5 5.1.1 Naming Conventions . . . . . . . . . . . . . . . . . . 5
7.1 Management rules . . . . . . . . . . . . . . . . . . . . . 5 5.1.2 Metrics Defined by IETF . . . . . . . . . . . . . . . 5
7.1.1 Naming Conventions . . . . . . . . . . . . . . . . . . 5 5.1.3 Metrics Defined in Cooperation with Standards
7.1.2 Metrics defined by IETF . . . . . . . . . . . . . . . 5 bodies or Fora . . . . . . . . . . . . . . . . . . . . 5
7.1.3 Metrics defined in cooperation with other bodies . . . 5 5.1.4 Entreprise Metrics Registration . . . . . . . . . . . 6
7.1.4 Private Metrics registration . . . . . . . . . . . . . 6 5.2 Registration templates . . . . . . . . . . . . . . . . . . 6
7.2 Registration templates . . . . . . . . . . . . . . . . . . 6 5.2.1 IETF RFCs . . . . . . . . . . . . . . . . . . . . . . 6
7.2.1 IETF RFCs . . . . . . . . . . . . . . . . . . . . . . 6 5.2.2 Standards bodies and Fora . . . . . . . . . . . . . . 7
7.2.2 Other Organizations . . . . . . . . . . . . . . . . . 7 5.2.3 Enterprises . . . . . . . . . . . . . . . . . . . . . 7
7.2.3 Enterprises . . . . . . . . . . . . . . . . . . . . . 7 6. Initial IPPM registry definition . . . . . . . . . . . . . . . 8
8. Initial IPPM registry definition . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 16
9. Security Considerations . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 8.1 Normative References . . . . . . . . . . . . . . . . . . . . 16
10.1 Normative References . . . . . . . . . . . . . . . . . . . . 15 8.2 Informative References . . . . . . . . . . . . . . . . . . . 17
10.2 Informative References . . . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . 18 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. MIB information store, termed the Management Information Base or MIB.
objects are generally accessed through the Simple Network Management MIB objects are generally accessed through the Simple Network
Protocol (SNMP). Objects in the MIB are defined using the mechanisms Management Protocol (SNMP). Objects in the MIB are defined using the
defined in the Structure of Management Information (SMI). This memo mechanisms defined in the Structure of Management Information (SMI).
specifies a MIB module that is compliant to the SMIv2, which is This memo specifies a MIB module that is compliant to the SMIv2,
described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579
and STD 58, RFC 2580 [RFC2580]. [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 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; As specification of new metrics is a continuous
process, special care must be taken for the integration of future process, special care must be taken for the integration of future
standardized metrics; standardized metrics;
o As 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 and other areas of IETF to promote appropriate standards bodies (or fora) to promote consistent
consistent metrics, there is a need to permit registration of such metrics, a branch where other standards bodies can register their
metrics. metrics is provided to encourage IP performance metrics to have
OBJECT IDENTITIES rooted at a common point;
5. IPPM metrics Registry framework o Similarly, a branch is provided for registered enterprises to
register metrics.
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 3 main branches. The origin of the document
determines the node which branch the metric is identified in: defining the metrics determines the node which branch the metric is
identified in:
o Metrics defined by IETF are identified in the 'ietf' tree; o Metrics defined by IETF are identified in the
'ianaIppmIetfMetrics' tree;
o Metrics defined in cooperation with other organizations may be o Metrics defined in cooperation with standards bodies or fora may
identified in the 'otherOrganizations' tree. be identified in the 'ianaIppmForaMetrics' tree.
o Vendors may register private metrics in the 'enterprises' 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 and
the rules to manage the registry. 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.
6. 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. By now, the IPPM WG defined 33 metrics RFCs produced in the IPPM WG. To date, the IPPM WG defined 33
related to 7 topics: metrics related to 7 topics:
o IPPM Metrics for Measuring Connectivity, RFC 2678 [RFC2678]; o IPPM Metrics for Measuring Connectivity, RFC 2678 [RFC2678];
o One-way Delay Metrics, RFC 2679 [RFC2679]; o One-way Delay Metrics, RFC 2679 [RFC2679];
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];
skipping to change at page 5, line 4 skipping to change at page 4, line 34
o IPPM Metrics for Measuring Connectivity, RFC 2678 [RFC2678]; o IPPM Metrics for Measuring Connectivity, RFC 2678 [RFC2678];
o One-way Delay Metrics, RFC 2679 [RFC2679]; o One-way Delay Metrics, RFC 2679 [RFC2679];
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];
7. IANA considerations 5. IANA Considerations
This section describes the rules for the management of the registry This section describes the rules for the management of the registry
by IANA. by IANA.
7.1 Management rules 5.1 Management rules
7.1.1 Naming Conventions 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 The name of the metric in the registry must respect the SMIv2 rules
for descriptors ([RFC2578], section 3.1) and should be easily for descriptors defined in the section 3.1 of [RFC2578]:
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 Descriptors longer than 32 characters are not recommended;
o 'Type-P' prefix is removed. o Initial character must be a lower-case letter;
o '-' are removed; o Hyphens are not allowed;
o The letter following a '-' is changed to upper case; The following rules are applied to allocate the name and the
identifier of a metric:
o A node assigned to a metric is definitive and cannot be reused. 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 o If a new version of a metric is produced then it is assigned with
a new name and a new identifier. a new name and a new identifier.
7.1.2 Metrics defined by IETF 5.1.2 Metrics Defined by IETF
Such metrics are registered in the node ietf(1) after approval of the Such metrics are registered in the node ianaIppmIetfMetrics(1). The
document by the IESG. guidelines used for the existing metrics, and encouraged for new
metrics, are
The name always starts with the prefix 'ietf'. They are registered in o The name always starts with the prefix 'ietf'.
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 o 'Type-P' prefix is removed.
After approval of the document by the IESG, IANA will assign the o '-' are removed;
organization with a subtree under the branch otherOrganizations(2).
The organization registers metrics under the branch o The letter following a '-' is changed to upper case;
otherOrganizations(2), in the corresponding subtree. The name of the
metric always starts with the prefix of the organization. The prefix 5.1.3 Metrics Defined in Cooperation with Standards bodies or Fora
is the name of the subtree assigned to the organization.
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 Nothing prevents these bodies from registering metrics in their own
OBJECT INDENTIFIER trees. OBJECT INDENTIFIER trees.
7.1.4 Private Metrics registration 5.1.4 Entreprise Metrics Registration
IANA already assigns enterprises with unambiguous identifiers named IANA already assigns enterprises with unambiguous identifiers named
enterprise numbers or vendorID. See http://www.iana.org/numbers.html. enterprise numbers or vendorID. See
http://www.iana.org/numbers.html.
After approval of the document by the IESG, an enterprise may o An enterprise without an entreprise number should apply for one;
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 o IANA registers the metrics of an enterprise under the branch
subtree. ianaIppmEnterprisesMetrics(3), in the subtree corresponding to its
enterprise number.
Example: The enterprise Acme,which enterprise number is 100000, will o The name of the metric always starts with (an abbreviation of) the
register its metrics in the subtree name of the company.
ippmMetricsRegistry(x).enterprises(3).100000.
7.2 Registration templates For example, if Acme Networks has been assigned { enterprises 696 },
it will register its metrics in the subtree
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 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.
7.2.1 IETF RFCs 5.2.1 IETF RFCs
For each metric, that section would have a statement aka: For each metric, that section would have a statement aka:
IANA has registed the following Metric in the IANA-IPPM-METRICS-MIB: IANA has registed the following metric in the
IANA-IPPM-METRICS-REGISTRY-MIB:
ietfSomeNewMetricName OBJECT-IDENTITY ietfSomeNewMetricName OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The identifier for the Type-P-Some-New_Metric-Name DESCRIPTION "The identifier for the Type-P-Some-New_Metric-Name
metric." metric."
REFERENCE "RFCxxxx, section n." -- RFC-Editor fills in xxxx REFERENCE "RFCxxxx, section n." -- RFC-Editor fills in xxxx
::= { ietf nn } -- IANA assigns nn ::= { 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: For each metric, that section would have a statement aka:
IANA has registed the following Metric in the IANA-IPPM-METRICS-MIB: IANA has registed the following metric in the
IANA-IPPM-METRICS-REGISTRY-MIB:
orgSomeNewMetricName OBJECT-IDENTITY foraNameSomeNewMetricName OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The identifier for the Some-New_Metric-Name DESCRIPTION "The identifier for the Some-New_Metric-Name
metric." metric."
REFERENCE "URL, section n." -- link to the org document. REFERENCE "Specification title/revision/date, section n."
::= { org nn } -- org assigns nn ::= { foraEnterpriseNumber nn } -- IANA assigns nn
7.2.3 Enterprises 5.2.3 Enterprises
For each metric, that section would have a statement aka: For each metric, that section would have a statement aka:
Vendor has registed the following Metric: IANA has registed the following metric in the
IANA-IPPM-METRICS-REGISTRY-MIB:
vendorSomeNewMetricName OBJECT-IDENTITY vendorNameSomeNewMetricName OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The identifier for the Some-New_Metric-Name DESCRIPTION "The identifier for the Some-New_Metric-Name
metric." metric."
REFERENCE "URL, section n." -- link to the vendor document. REFERENCE "Specification title/revision/date, section n."
::= { vendorID nn } -- vendor assigns nn ::= { vendorEnterpriseNumber nn } -- IANA assigns nn
8. Initial IPPM registry definition 6. Initial IPPM registry definition
IANA-IPPM-METRICS-REGISTRY 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;
ippmMetricsRegistry MODULE-IDENTITY ianaIppmMetricsRegistry MODULE-IDENTITY
REVISION "200405190000Z" -- May 19th, 2004 LAST-UPDATED "200406280000Z" -- June 28th, 2004
ORGANIZATION "IETF IPPM working Group" ORGANIZATION "IANA"
CONTACT-INFO " CONTACT-INFO "Internet Assigned Numbers Authority
Emile STEPHAN
France Telecom R&D Postal: ICANN
Tel: +1 33 2 96 05 36 10 4676 Admiralty Way, Suite 330
E-mail: emile.stephan@francetelecom.com Marina del Rey, CA 90292
Postal: 2, avenue Pierre Marzin
Lannion, FRANCE 22307 Tel: +1 310 823 9358
E-Mail: iana@iana.org"
Send comments to ippm@ietf.org
Mailing list subscription info:
https://www1.ietf.org/mailman/listinfo/ippm "
DESCRIPTION DESCRIPTION
"This memo defines a registry of the IPPM working group
metrics. "This module defines a registry for IP Performance (IPPM) Metrics.
Copyright (C) The Internet Society (2004). This version of
this MIB module is part of RFC yyyy; see the RFC itself for The registry is administred by IANA.
full legal notices."
REVISION "200405190000Z" -- May 19th, 2004 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 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). The initial version of
this MIB module was published in RFC yyyy; for full legal notices
see the RFC itself or see:
http://www.ietf.org/copyrights/ianamib.html. "
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200406280000Z" -- June 28th, 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
ietf OBJECT IDENTIFIER ::= { ippmMetricsRegistry 1 } ianaIppmIetfMetrics OBJECT-IDENTITY
otherOrganizations OBJECT IDENTIFIER ::= { ippmMetricsRegistry 2 } STATUS current
enterprises OBJECT IDENTIFIER ::= { ippmMetricsRegistry 3 } DESCRIPTION
"Registration point for IP Performance (IPPM) Metrics
defined by the IETF."
::= { 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
"The identifier for the Type-P-Instantaneous-Unidirectional- "Type-P-Instantaneous-Unidirectional-Connectivity"
Connectivity metric."
REFERENCE "RFC2678, section 2." REFERENCE "RFC2678, section 2."
::={rfc 1} ::= { ianaIppmIetfMetrics 1}
ietfInstantBidirConnectivity OBJECT-IDENTITY ietfInstantBidirConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Instantaneous-Bidirectional- "Type-P-Instantaneous-Bidirectional-Connectivity"
Connectivity metric."
REFERENCE "RFC2678, section 3." REFERENCE "RFC2678, section 3."
::={rfc 2} ::= { ianaIppmIetfMetrics 2}
ietfIntervalUnidirConnectivity OBJECT-IDENTITY ietfIntervalUnidirConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Interval-Unidirectional- "Type-P-Interval-Unidirectional-Connectivity"
Connectivity metric."
REFERENCE "RFC2678, section 4." REFERENCE "RFC2678, section 4."
::= { rfc 3 } ::= { ianaIppmIetfMetrics 3 }
ietfIntervalBidirConnectivity OBJECT-IDENTITY ietfIntervalBidirConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Interval-Bidirectional- "Type-P-Interval-Bidirectional-Connectivity"
Connectivity metric."
REFERENCE "RFC2678, section 5." REFERENCE "RFC2678, section 5."
::= { rfc 4 } ::= { ianaIppmIetfMetrics 4 }
ietfIntervalTemporalConnectivity OBJECT-IDENTITY ietfIntervalTemporalConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P1-P2-Interval-Temporal- "Type-P1-P2-Interval-Temporal-Connectivity"
Connectivity metric."
REFERENCE "RFC2678, section 6." REFERENCE "RFC2678, section 6."
::= { rfc 5 } ::= { ianaIppmIetfMetrics 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
"The identifier for the Type-P-One-way-Delay metric." "Type-P-One-way-Delay"
REFERENCE "RFC2679, section 3." REFERENCE "RFC2679, section 3."
::= { rfc 6 } ::= { ianaIppmIetfMetrics 6 }
ietfOneWayDelayPoissonStream OBJECT-IDENTITY ietfOneWayDelayPoissonStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-Delay-Poisson-Stream "Type-P-One-way-Delay-Poisson-Stream"
metric."
REFERENCE "RFC2679, section 4." REFERENCE "RFC2679, section 4."
::= { rfc 7 } ::= { ianaIppmIetfMetrics 7 }
ietfOneWayDelayPercentile OBJECT-IDENTITY ietfOneWayDelayPercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-Delay-Percentile "Type-P-One-way-Delay-Percentile"
metric."
REFERENCE "RFC2679, section 5.1." REFERENCE "RFC2679, section 5.1."
::= { rfc 8 } ::= { ianaIppmIetfMetrics 8 }
ietfOneWayDelayMedian OBJECT-IDENTITY ietfOneWayDelayMedian OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-Delay-Median metric." "Type-P-One-way-Delay-Median"
REFERENCE "RFC2679, section 5.2." REFERENCE "RFC2679, section 5.2."
::= { rfc 9 } ::= { ianaIppmIetfMetrics 9 }
ietfOneWayDelayMinimum OBJECT-IDENTITY ietfOneWayDelayMinimum OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-Delay-Minimum metric." "Type-P-One-way-Delay-Minimum"
REFERENCE "RFC2679, section 5.3." REFERENCE "RFC2679, section 5.3."
::= { rfc 10 } ::= { ianaIppmIetfMetrics 10 }
ietfOneWayDelayInversePercentile OBJECT-IDENTITY ietfOneWayDelayInversePercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-Delay-Inverse- "Type-P-One-way-Delay-Inverse-Percentile"
Percentile metric. "
REFERENCE "RFC2679, section 5.4." REFERENCE "RFC2679, section 5.4."
::= { rfc 11 } ::= { ianaIppmIetfMetrics 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
"The identifier for the Type-P-One-way-Packet-Loss metric." "Type-P-One-way-Packet-Loss"
REFERENCE "RFC2680, section 2." REFERENCE "RFC2680, section 2."
::= { rfc 12 } ::= { ianaIppmIetfMetrics 12 }
ietfOneWayPktLossPoissonStream OBJECT-IDENTITY ietfOneWayPktLossPoissonStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-Packet-Loss-Poisson- "Type-P-One-way-Packet-Loss-Poisson-Stream"
Stream metric."
REFERENCE "RFC2680, section 3." REFERENCE "RFC2680, section 3."
::= { rfc 13 } ::= { ianaIppmIetfMetrics 13 }
ietfOneWayPktLossAverage OBJECT-IDENTITY ietfOneWayPktLossAverage OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-Packet-Loss-Average "Type-P-One-way-Packet-Loss-Average"
metric."
REFERENCE "RFC2680, section 4." REFERENCE "RFC2680, section 4."
::= { rfc 14 } ::= { ianaIppmIetfMetrics 14 }
-- TODO remnae as V5 in v5 dir --
-- 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
"The identifier for the Type-P-Round-trip-Delay metric." "Type-P-Round-trip-Delay"
REFERENCE " section 2 of the rfc2681." REFERENCE " section 2 of the rfc2681."
::= { rfc 15 } ::= { ianaIppmIetfMetrics 15 }
ietfRoundTripDelayPoissonStream OBJECT-IDENTITY ietfRoundTripDelayPoissonStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Round-trip-Delay-Poisson "Type-P-Round-trip-Delay-Poisson-Stream"
-Stream metric."
REFERENCE "RFC2681, section 4." REFERENCE "RFC2681, section 4."
::= { rfc 16 } ::= { ianaIppmIetfMetrics 16 }
ietfRoundTripDelayPercentile OBJECT-IDENTITY ietfRoundTripDelayPercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Round-trip-Delay-Percentile "Type-P-Round-trip-Delay-Percentile"
metric."
REFERENCE "RFC2681, section 4.1." REFERENCE "RFC2681, section 4.1."
::= { rfc 17 } ::= { ianaIppmIetfMetrics 17 }
ietfRoundTripDelayMedian OBJECT-IDENTITY ietfRoundTripDelayMedian OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Round-trip-Delay-Median "Type-P-Round-trip-Delay-Median"
metric."
REFERENCE "RFC2681, section 4.2." REFERENCE "RFC2681, section 4.2."
::= { rfc 18 } ::= { ianaIppmIetfMetrics 18 }
ietfRoundTripDelayMinimum OBJECT-IDENTITY ietfRoundTripDelayMinimum OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Round-trip-Delay-Minimum "Type-P-Round-trip-Delay-Minimum"
metric."
REFERENCE "RFC2681, section 4.3." REFERENCE "RFC2681, section 4.3."
::= { rfc 19 } ::= { ianaIppmIetfMetrics 19 }
ietfRoundTripDelayInversePercentile OBJECT-IDENTITY ietfRoundTripDelayInvPercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Round-trip-Inverse-Percentile "Type-P-Round-trip-Inverse-Percentile"
metric."
REFERENCE "RFC2681, section 4.4." REFERENCE "RFC2681, section 4.4."
::= { rfc 20 } ::= { ianaIppmIetfMetrics 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
"The identifier for the Type-P-One-Way-Loss-Distance-Stream "Type-P-One-Way-Loss-Distance-Stream"
metric."
REFERENCE " RFC3357, section 5.4.1." REFERENCE " RFC3357, section 5.4.1."
::={ rfc 21} ::={ ianaIppmIetfMetrics 21}
ietfOneWayLossPeriodStream OBJECT-IDENTITY ietfOneWayLossPeriodStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-Way-Loss-Period-Stream "Type-P-One-Way-Loss-Period-Stream"
metric."
REFERENCE " RFC3357, section 5.4.2." REFERENCE " RFC3357, section 5.4.2."
::={ rfc 22} ::={ ianaIppmIetfMetrics 22}
ietfOneWayLossNoticeableRate OBJECT-IDENTITY ietfOneWayLossNoticeableRate OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-Way-Loss-Noticeable-Rate "Type-P-One-Way-Loss-Noticeable-Rate"
metric."
REFERENCE " RFC3357, section 6.1." REFERENCE " RFC3357, section 6.1."
::= { rfc 23 } ::= { ianaIppmIetfMetrics 23 }
ietfOneWayLossPeriodTotal OBJECT-IDENTITY ietfOneWayLossPeriodTotal OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-Way-Loss-Period-Total "Type-P-One-Way-Loss-Period-Total"
metric."
REFERENCE " RFC3357, section 6.2." REFERENCE " RFC3357, section 6.2."
::= { rfc 24 } ::= { ianaIppmIetfMetrics 24 }
ietfOneWayLossPeriodLengths OBJECT-IDENTITY ietfOneWayLossPeriodLengths OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-Way-Loss-Period-Lengths "Type-P-One-Way-Loss-Period-Lengths"
metric."
REFERENCE " RFC3357, section 6.3." REFERENCE " RFC3357, section 6.3."
::= { rfc 25 } ::= { ianaIppmIetfMetrics 25 }
ietfOneWayInterLossPeriodLengths OBJECT-IDENTITY ietfOneWayInterLossPeriodLengths OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-Way-Inter-Loss-Period- "Type-P-One-Way-Inter-Loss-Period-Lengths"
Lengths metric."
REFERENCE " RFC3357, section 6.4." REFERENCE " RFC3357, section 6.4."
::= { rfc 26 } ::= { ianaIppmIetfMetrics 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
"The identifier for the Type-P-One-way-ipdv metric." "Type-P-One-way-ipdv"
REFERENCE " RFC3393, section 2." REFERENCE " RFC3393, section 2."
::= { rfc 27 } ::= { ianaIppmIetfMetrics 27 }
ietfOneWayIpdvPoissonStream OBJECT-IDENTITY ietfOneWayIpdvPoissonStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-ipdv-Poisson-stream "Type-P-One-way-ipdv-Poisson-stream"
metric."
REFERENCE " RFC3393, section 3." REFERENCE " RFC3393, section 3."
::= { rfc 28 } ::= { ianaIppmIetfMetrics 28 }
ietfOneWayIpdvPercentile OBJECT-IDENTITY ietfOneWayIpdvPercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-ipdv-percentile metric." "Type-P-One-way-ipdv-percentile"
REFERENCE " RFC3393, section 4.3." REFERENCE " RFC3393, section 4.3."
::= { rfc 29 } ::= { ianaIppmIetfMetrics 29 }
ietfOneWayIpdvInversePercentile OBJECT-IDENTITY ietfOneWayIpdvInversePercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-ipdv-inverse "Type-P-One-way-ipdv-inverse-percentile"
-percentile metric."
REFERENCE " RFC3393, section 4.4." REFERENCE " RFC3393, section 4.4."
::= { rfc 30 } ::= { ianaIppmIetfMetrics 30 }
ietfOneWayIpdvJitter OBJECT-IDENTITY ietfOneWayIpdvJitter OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-ipdv-jitter metric." "Type-P-One-way-ipdv-jitter"
REFERENCE " RFC3393, section 4.5." REFERENCE " RFC3393, section 4.5."
::= { rfc 31 } ::= { ianaIppmIetfMetrics 31 }
ietfOneWayPeakToPeakIpdv OBJECT-IDENTITY ietfOneWayPeakToPeakIpdv OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-peak-to-peak-ipdv "Type-P-One-way-peak-to-peak-ipdv"
metric."
REFERENCE " RFC3393, section 4.6." REFERENCE " RFC3393, section 4.6."
::= { rfc 32 } ::= { ianaIppmIetfMetrics 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
"The identifier for the Type-P-One-way-Delay-Periodic-Stream "Type-P-One-way-Delay-Periodic-Stream"
metric."
REFERENCE " RFC3432, section 4." REFERENCE " RFC3432, section 4."
::= { rfc 33 } ::= { ianaIppmIetfMetrics 33 }
END END
9. 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
modules that define management objects. This document has therefore modules that define management objects. This document has therefore
no impact on the security of the Internet. no impact on the security of the Internet.
10. References 8. 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 8.1 Normative References
Protocol (ICMPv6) for the Internet Protocol Version 6
(IPv6) Specification", RFC 2463, December 1998.
[RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IPv6 Specification", RFC 2473, December 1998. IANA Considerations Section in RFCs", BCP 26, RFC 2434,
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., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999. Conventions for SMIv2", STD 58, RFC 2579, April 1999.
skipping to change at page 16, line 25 skipping to change at page 16, line 48
[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
Delay Metric for IPPM", RFC 2681, September 1999. 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 [RFC3357] Koodli, R. and R. Ravikanth, "One-way Loss Pattern Sample
Metrics", RFC 3357, August 2002. Metrics", RFC 3357, August 2002.
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation [RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation
Metric for IP Performance Metrics (IPPM)", RFC 3393, Metric for IP Performance Metrics (IPPM)", RFC 3393,
November 2002. November 2002.
[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.
10.2 Informative References 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, [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.
[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, [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
2 avenue Pierre Marzin 2 avenue Pierre Marzin
Lannion, F-22307 Lannion, F-22307
Fax: +33 2 96 05 18 52 Fax: +33 2 96 05 18 52
EMail: emile.stephan@francetelecom.com EMail: emile.stephan@francetelecom.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification can attempt made to obtain a general license or permission for the use of
be obtained from the IETF Secretariat. such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at
Director. ietf-ipr@ietf.org.
Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Disclaimer of Validity
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
and distributed, in whole or in part, without restriction of any ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
kind, provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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 Copyright Statement
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an Copyright (C) The Internet Society (2004). This document is subject
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING to the rights, licenses and restrictions contained in BCP 78, and
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING except as set forth therein, the authors retain all their rights.
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.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

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