draft-ietf-ippm-metrics-registry-00.txt   draft-ietf-ippm-metrics-registry-01.txt 
Network Working Group E. Stephan Network Working Group E. Stephan
Internet Draft France Telecom R&D Internet Draft France Telecom R&D
Document: draft-ietf-ippm-metrics-registry-00.txt June 18, 2002 Document: draft-ietf-ippm-metrics-registry-01.txt June 24, 2002
IPPM metrics registry IPPM metrics registry
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1]. all provisions of Section 10 of RFC2026 [1].
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 other
skipping to change at page 1, line 43 skipping to change at page 1, line 43
provides an OBJECT IDENTIFIER to each metric currently standardized provides an OBJECT IDENTIFIER to each metric currently standardized
by the IPPM WG. It defines the rules for the identification of the by the IPPM WG. It defines the rules for the identification of the
metrics standardized in the future. metrics standardized in the future.
Table of Contents Table of Contents
1. Introduction................................................2 1. Introduction................................................2
2. The IPPM Framework..........................................2 2. The IPPM Framework..........................................2
3. Overview....................................................2 3. Overview....................................................2
4. IPPM metrics Registry framework.............................2 4. IPPM metrics Registry framework.............................2
4.1. Metrics specified in a RFC..................................3 4.1. Metrics registry format.....................................3
4.2. Metrics specified in a WG draft.............................4 4.2. Metrics specified in a RFC..................................3
4.3. Metrics specified in other documents........................5 4.3. Metrics specified in a WG draft.............................4
4.4. Metrics specified in other documents........................5
5. Initial IPPM registry.......................................5 5. Initial IPPM registry.......................................5
6. References..................................................6 6. References.................................................12
7. Author's Addresses..........................................7 7. Author's Addresses.........................................12
1. Introduction 1. Introduction
This memo defines a registry of the IPPM working group metrics. It This memo defines a registry of the IPPM working group metrics. It
provides an OBJECT IDENTIFIER to each metric currently standardized provides an OBJECT IDENTIFIER to each metric currently standardized
by the IPPM WG. It defines the rules for the identification of the by the IPPM WG. It defines the rules for the identification of the
metrics standardized in the future. metrics standardized in the future.
2. The IPPM Framework 2. The IPPM Framework
skipping to change at page 2, line 52 skipping to change at page 2, line 52
interoperability; interoperability;
+ Specification of new metrics is a continuous process, special + Specification of new metrics is a continuous process, special
care must be taken for the integration of the future care must be taken for the integration of the future
standardized metrics. standardized metrics.
4. IPPM metrics Registry framework 4. IPPM metrics Registry framework
MIBs need OBJECT INDENTIFIER to refer precisely to the standardized MIBs need OBJECT INDENTIFIER to refer precisely to the standardized
metrics. The registry associates an OBJECT IDENTIFIER to each metric. As metrics. The registry associates an OBJECT IDENTIFIER to each metric. As
an example onewayDelay and onewayDelayPoissonStream have different an example oneWayDelay and oneWayDelayPoissonStream have different
identifiers. identifiers.
The registry has three root branches. The category of the document The registry has three root branches. The category of the document
determines the node the branch the metric is identified in: determines the node the branch the metric is identified in:
+ Metrics defined in a RFC are identified in the 'rfc' tree; + Metrics defined in a RFC are identified in the 'rfc' tree;
+ Metrics defined in a draft of a working group are identified in + Metrics defined in a draft of a working group are identified in
the 'draft' tree; the 'draft' tree;
+ Metrics defined elsewhere may be identified in the 'other' 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 The name of the metric has to respect ASN.1 constraints. The name has to
skipping to change at page 3, line 30 skipping to change at page 3, line 30
uniforms the metrics names. uniforms the metrics names.
Each sub-tree has specific rules to assign a node to a metric. Each sub-tree has specific rules to assign a node to a metric.
Each metrics specification will include a section describing its metrics Each metrics specification will include a section describing its metrics
identifiers. identifiers.
IPPM metrics are numbered using the specifications submissions order and IPPM metrics are numbered using the specifications submissions order and
the metrics definitions order in each memo. the metrics definitions order in each memo.
4.1. Metrics specified in a RFC 4.1. Metrics registry format
4.1.1. Rules 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.
4.2. Metrics specified in a RFC
4.2.1. Rules
The metrics specified in a RFC are registered in the node rfc(1). The metrics specified in a RFC are registered in the node rfc(1).
They are numbered using the RFC order and the metrics definitions order They are numbered using the RFC order and the metrics definitions order
in each memo. in each memo.
The value assigned to a metric is definitive and can not be reused. The value assigned to a metric is definitive and can not be reused.
4.1.2. Current WG RFC integration in the registry 4.2.2. Current WG RFC integration in the registry
These rules are applied to initiate the registry. The metrics already These rules are applied to initiate the registry. The metrics already
standardized are identified in the section 5 'IPPM registry' of this standardized are identified in the section 5 'IPPM metrics registry' of
memo. this memo. The registry definition should be respectful of the format
defined in "4.1 Metrics registry format".
4.1.3. Identification of the metrics standardized in future RFC 4.2.3. Identification of the metrics standardized in future RFC
The specification of metrics is a continuous process. The same rules are The specification of metrics is a continuous process. The same rules are
applied to number the metrics of the new RFC. The identifiers are applied to number the metrics of the new RFC. The identifiers are
included in the section 'Standard metrics registry' of the RFC which included in the section 'Standard metrics registry' of the RFC.
lists the identifier of the metrics at the format 'metricName OBJECT
IDENTIFIER ::= { rfc <metricNode> }'
The temporary identifiers assigned previously to the draft corresponding The status of the identifiers assigned previously to the draft
to the new RFC are considered obsolete and may be reassigned. corresponding to the new RFC are set up to 'obsolete' and may not be
reassigned.
4.2. Metrics specified in a WG draft 4.3. Metrics specified in a WG draft
Usually, metrics are implemented during the specification process. At Usually, metrics are implemented during the specification process. At
this step, a metric is not identified as an IPPM metric. There is a need this step, a metric is not identified as an IPPM metric. There is a need
to provide temporary metric identifiers to facilitate software to provide temporary metric identifiers to facilitate software
integration and to permit interoperability measurement among different integration and to permit interoperability measurement among different
implementations. Otherwise the interoperability will be extremely implementations. Otherwise the interoperability will be extremely
limited du to the fact that implementers will choose arbitrary values to limited du to the fact that implementers will choose arbitrary values to
identify the new metrics. identify the new metrics.
4.2.1. Rules 4.3.1. Rules
The metrics specified in an IPPM draft are registered in the node The metrics specified in an IPPM draft are registered in the node
draft(2). draft(2).
A draft is more or less released two times a year. It looks ambiguous to A draft is more or less released two times a year. It looks ambiguous to
use the chronological order of the successive drafts submissions to use the chronological order of the successive drafts submissions to
numbered the metrics because usually the metric name does not change numbered the metrics because usually the metric name does not change
among the different releases. On the other hand new metrics may be added among the different releases. On the other hand new metrics may be added
in successive releases of a draft. in successive releases of a draft.
When a draft disappears the temporary identifiers assigned to the 4.3.2. Current WG drafts integration in the registry
metrics defined in the draft are considered obsolete and may be
reassigned.
4.2.2. Current WG drafts integration in the registry
The current drafts are numbered using the submission orders of their The current drafts are numbered using the submission orders of their
current release and using the order of the metrics definition in each current release and using the order of the metrics definition in each
memo. memo.
The previous rules are applied to initiate the registry. The metrics The previous rules are applied to initiate the registry. The metrics
specified in current WG drafts are identified in the section 5 'IPPM specified in current WG drafts are identified in the section 5 'draft
registry' of this memo. metrics registry' of this memo. The registry definition should be
respectful of the format defined in "4.1 Metrics registry format".
4.2.3. Identification of a metric added to an existing WG draft 4.3.3. Identification of a metric added to an existing WG draft
Despite new metrics are rarely created in successive releases of a Despite new metrics are rarely created in successive releases of a
draft, an arbitrary metric identifier may be provided by the IPPM WG to draft, an arbitrary metric identifier may be provided by the IPPM WG to
identify the new metric. identify the new metric.
The identifier is added in the section named 'Draft metrics registry' of The identifier is added in the section named 'Draft metrics registry' of
the draft. This section list the identifier of the metrics at the format the draft. The registry definition should be respectful of the format
'draftMetricName OBJECT IDENTIFIER ::= { draft <metricNode> }' defined in "4.1 Metrics registry format".
4.2.4. Identification of the metrics defined in future WG drafts 4.3.4. Identification of the metrics defined in future WG drafts
They are numbered using the chronological orders of the first submission They are numbered using the chronological orders of the first submission
of the draft and using the order of the metrics definition in each memo. of the draft and using the order of the metrics definition in each memo.
These identifiers are included in the draft in a section named 'Draft These identifiers are included in the draft in a section named 'Draft
metrics registry'. This section list the identifier of the metrics at metrics registry'. The registry definition should be respectful of the
the format 'draftMetricName OBJECT IDENTIFIER ::= { draft <metricNode> format defined in "4.1 Metrics registry format".
}'
4.3. Metrics specified in other documents The name of the metric starts with 'draft' to clearly distinguish the
draft OBJECT INDENTIFIER from the its future standard OBJECT
INDENTIFIER.
Example:
Consider a IPPM WG draft that defines the multicast metric Type-P-
Multicast-Instantaneous-Hop-One-way-Delay.
The name of this metric in the section 'Draft metrics registry' is
'draftMulticastInstantaneousHopOneWayDelay'. When this draft will go to
RFC, the metric name will become 'multicastInstantaneousHopOneWayDelay'.
4.4. Metrics specified in other documents
Other metrics may be associated with identifiers in the sub tree Other metrics may be associated with identifiers in the sub tree
other(4). The identifiers are provided by the IPPM WG. other(4). The identifiers are provided by the IPPM WG.
These identifiers are included in the corresponding document in a These identifiers are included in the corresponding document in a
section named 'IPPM registry identifiers'. This section list the section named 'IPPM registry identifiers'. The registry definition
identifier of the metrics at the format 'MetricName OBJECT IDENTIFIER should be respectful of the format defined in "4.1 Metrics registry
::= { other <metricNode> }' format".
5. Initial IPPM registry 5. Initial IPPM registry
ippm OBJECT IDENTIFIER ::= XXXX -- To be assigned IPPM-METRICS-REGISTRY DEFINITIONS ::= BEGIN
registry OBJECT IDENTIFIER ::= { ippm 1 }
IMPORTS
MODULE-IDENTITY
FROM SNMPv2-SMI;
ippmMetricsRegistry MODULE-IDENTITY
LAST-UPDATED "200206241100Z" -- June 24, 2002
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 "200206241100z"
DESCRIPTION
"Each metric identifier is defined in a OBJECT IDENTITY macro."
::= { ippm 1 }
--
-- ippm OBJECT IDENTIFIER ::= XXXX -- To be assigned
--
rfc OBJECT IDENTIFIER ::= { registry 1 } rfc OBJECT IDENTIFIER ::= { registry 1 }
draft OBJECT IDENTIFIER ::= { registry 2 } draft OBJECT IDENTIFIER ::= { registry 2 }
other OBJECT IDENTIFIER ::= { registry 4 } other OBJECT IDENTIFIER ::= { registry 4 }
-- --
-- Registry of the metrics of the IPPM WG RFCs -- Registry of the metrics of the IPPM WG RFCs
-- --
instantaneousUnidirectionalConnectivity OBJECT IDENTIFIER::={rfc 1} --
instantaneousBidirectionalConnectivity OBJECT IDENTIFIER ::={rfc 2} -- RFC 2678 " IPPM Metrics for Measuring Connectivity"
intervalUnidirectionalConnectivity OBJECT IDENTIFIER ::= { rfc 3 } --
intervalBidirectionalConnectivity OBJECT IDENTIFIER ::= { rfc 4 }
intervalTemporalConnectivity OBJECT IDENTIFIER ::= { rfc 5 } instantaneousUnidirectionalConnectivity OBJECT-IDENTITY
onewayDelay OBJECT IDENTIFIER ::= { rfc 6 } STATUS current
onewayDelayPoissonStream OBJECT IDENTIFIER ::= { rfc 7 } DESCRIPTION
onewayDelayPercentile OBJECT IDENTIFIER ::= { rfc 8 } "The identifier for the Type-P-Instantaneous-Unidirectional-
onewayDelayMedian OBJECT IDENTIFIER ::= { rfc 9 } Connectivity metric."
onewayDelayMinimum OBJECT IDENTIFIER ::= { rfc 10 } REFERENCE "RFC2678, section 2."
onewayDelayInversePercentile OBJECT IDENTIFIER ::= { rfc 11 } ::={rfc 1}
onewayPacketLoss OBJECT IDENTIFIER ::= { rfc 12 }
onewayPacketLossPoissonStream OBJECT IDENTIFIER ::= { rfc 13 } instantaneousBidirectionalConnectivity OBJECT-IDENTITY
onewayPacketLossAverage OBJECT IDENTIFIER ::= { rfc 14 } STATUS current
roundtripDelay OBJECT IDENTIFIER ::= { rfc 15 } DESCRIPTION
roundtripDelayPoissonStream OBJECT IDENTIFIER ::= { rfc 16 } "The identifier for the Type-P-Instantaneous-Bidirectional-
roundtripDelayPercentile OBJECT IDENTIFIER ::= { rfc 17 } Connectivity metric."
roundtripDelayMedian OBJECT IDENTIFIER ::= { rfc 18 } REFERENCE "RFC2678, section 3."
roundtripDelayMinimum OBJECT IDENTIFIER ::= { rfc 19 } ::={rfc 2}
roundtripDelayInversePercentile OBJECT IDENTIFIER ::= { rfc 20 }
intervalUnidirectionalConnectivity OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The identifier for the Type-P-Interval-Unidirectional-
Connectivity metric."
REFERENCE "RFC2678, section 4."
::= { rfc 3 }
intervalBidirectionalConnectivity 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."
Type-P-One-way-Delay
::= { 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
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"
--
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 }
-- --
-- Registry of the metrics of the IPPM WG drafts -- Registry of the metrics of the IPPM WG drafts
-- --
-- --
-- One-way Loss Pattern Sample Metrics draft -- One-way Loss Pattern Sample Metrics draft
-- --
oneWayLossDistanceStream OBJECT IDENTIFIER::={draft 1} draftOneWayLossDistanceStream OBJECT-IDENTITY
oneWayLossPeriodStream OBJECT IDENTIFIER ::={draft 2} STATUS current
oneWayLossDistanceStream OBJECT IDENTIFIER ::= { draft 3 } DESCRIPTION
oneWayLossPeriodStream OBJECT IDENTIFIER ::= { draft 4 } "The draft identifier for the Type-P-One-Way-Loss-Distance-
oneWayLossDistanceStream OBJECT IDENTIFIER ::= { draft 5 } Stream metric."
oneWayLossPeriodStream OBJECT IDENTIFIER ::= { draft 6 } REFERENCE "Work in progress"
oneWayLossNoticeableRate OBJECT IDENTIFIER ::= { draft 7 } ::={draft 1}
oneWayLossPeriodTotal OBJECT IDENTIFIER ::= { draft 8 }
oneWayLossPeriodLengths OBJECT IDENTIFIER ::= { draft 9 } draftOneWayLossPeriodStream OBJECT-IDENTITY
oneWayInterLossPeriodLengths OBJECT IDENTIFIER ::= { draft 10 } STATUS current
DESCRIPTION
"The draft identifier for the Type-P-One-Way-Loss-Period-Stream
metric."
REFERENCE "Work in progress"
::={draft 2}
draftOneWayLossNoticeableRate OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The draft identifier for the Type-P-One-Way-Loss-Noticeable-
Rate metric."
REFERENCE "Work in progress"
::= { draft 3 }
draftOneWayLossPeriodTotal OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The draft identifier for the Type-P-One-Way-Loss-Period-Total
metric."
REFERENCE "Work in progress"
::= { draft 4 }
draftOneWayLossPeriodLengths OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The draft identifier for the Type-P-One-Way-Loss-Period-Lengths
metric."
REFERENCE "Work in progress"
::= { draft 5 }
draftOneWayInterLossPeriodLengths OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The draft identifier for the Type-P-One-Way-Inter-Loss-Period-
Lengths metric."
REFERENCE "Work in progress"
::= { draft 6 }
-- --
-- Network performance measurement with periodic streams draft -- Network performance measurement with periodic streams draft
-- --
oneWayDelayPeriodicStream OBJECT IDENTIFIER ::= { draft 11 } draftOneWayDelayPeriodicStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The draft identifier for the Type-P-One-way-Delay-Periodic-
Stream metric."
REFERENCE "Work in progress"
::= { draft 7 }
-- --
-- IP Packet Delay Variation Metrics draft -- IP Packet Delay Variation Metrics draft
-- --
oneWayIpdv OBJECT IDENTIFIER ::= { draft 12 } draftOneWayIpdv OBJECT-IDENTITY
oneWayIpdvPoissonStream OBJECT IDENTIFIER ::= { draft 13 } STATUS current
oneWayIpdvPercentile OBJECT IDENTIFIER ::= { draft 14 } DESCRIPTION
oneWayIpdvJitter OBJECT IDENTIFIER ::= { draft 15 } "The draft identifier for the Type-P-One-way-ipdv metric."
oneWayPeakToPeakIpdv OBJECT IDENTIFIER ::= { draft 16 } REFERENCE "Work in progress"
::= { draft 8 }
draftOneWayIpdvPoissonStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The draft identifier for the Type-P-One-way-ipdv-Poisson-stream
metric."
REFERENCE "Work in progress"
::= { draft 9 }
draftOneWayIpdvPercentile OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The draft identifier for the Type-P-One-way-ipdv-percentile
metric."
REFERENCE "Work in progress"
::= { draft 10 }
draftOneWayIpdvJitter OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The draft identifier for the Type-P-One-way-ipdv-jitter
metric."
REFERENCE "Work in progress"
::= { draft 11 }
draftOneWayPeakToPeakIpdv OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The draft identifier for the Type-P-One-way-peak-to-peak-ipdv
metric."
REFERENCE "Work in progress"
::= { draft 12 }
-- --
-- Metrics registry from other documents -- Metrics registry from other documents
-- --
END
6. References 6. References
[1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996. 9, RFC 2026, October 1996.
[2] Mahdavi J. and V. Paxson, "IPPM Metrics for Measuring [2] Mahdavi J. and V. Paxson, "IPPM Metrics for Measuring
Connectivity", RFC 2678, September 1999. Connectivity", RFC 2678, September 1999.
[3] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Delay [3] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Delay
Metric for IPPM", RFC 2679, September 1999. Metric for IPPM", RFC 2679, September 1999.
[4] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Packet [4] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Packet
 End of changes. 

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