draft-ietf-ippm-metrics-registry-01.txt   draft-ietf-ippm-metrics-registry-02.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-02.txt March 1st, 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 41
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 registry format.....................................3 4.1. Metrics registry template...................................3
4.2. Metrics specified in a RFC..................................3 4.2. Initial IPPM metrics registry...............................4
4.3. Metrics specified in a WG draft.............................4 4.3. IPPM registry management....................................4
4.4. Metrics specified in other documents........................5 4.4. Identification of metric from other organization............4
5. Initial IPPM registry.......................................5 5. Initial IPPM registry.......................................4
6. References.................................................12 6. Change since release 00....................................11
7. Author's Addresses.........................................12 7. Change since release 01....................................11
8. References.................................................11
9. 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 51 skipping to change at page 2, line 52
+ Metrics identifiers are needed to allow measurement + Metrics identifiers are needed to allow measurement
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.
an example oneWayDelay and oneWayDelayPoissonStream have different
As an example oneWayDelay and oneWayDelayPoissonStream have different
identifiers. identifiers.
The registry has three root branches. The category of the document The registry has 2 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
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
start with a lower case. The letter - is forbidden (more or less) in the
name. In a way to preserve the readability of the metric name the
letters following a - are forced to upper case.
Sometime the name of the metric starts with 'Type-P'. It depends on the
document not the semantic of the metric. In the registry it is removed
from the name of the metric to reduce the length of the name and to
uniforms the metrics names.
Each sub-tree has specific rules to assign a node to a metric.
Each metrics specification will include a section describing its metrics
identifiers.
IPPM metrics are numbered using the specifications submissions order and The name of the metric has to respect ASN.1 constraints. The name has
the metrics definitions order in each memo. to start with a lower case. The letter - is forbidden (more or less)
in the name. In a way to preserve the readability of the metric name
the letters following a - are forced to upper case.
4.1. Metrics registry format Sometime the name of the metric starts with 'Type-P'. It depends on
the document not the semantic of the metric. In the registry it is
removed from the name of the metric to reduce the length of the name
and to uniforms the metrics names.
Each memo includes a registry where are identified the metrics. The name Each metrics specification will include a section describing its
of the section where is defined the registry terminate by 'metrics metrics identifiers.
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.1. Metrics registry template
4.2.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.
The metrics specified in a RFC are registered in the node rfc(1). IPPM-XXX-METRICS-REGISTRY DEFINITIONS ::= BEGIN
They are numbered using the RFC order and the metrics definitions order XXXMetricsRegistry MODULE-IDENTITY
in each memo. DESCRIPTION
" This memo defines a registry for XXX metrics."
::= { xxx N }
The value assigned to a metric is definitive and can not be reused. xxxMetric1Name OBJECT-IDENTITY
DESCRIPTION
"The identifier for the metric1."
REFERENCE
"xxx, section x."
::= { rfc i }
4.2.2. Current WG RFC integration in the registry xxxMetric2Name OBJECT-IDENTITY
DESCRIPTION
"The identifier for the metric1."
REFERENCE
"xxx, section y."
::= { rfc j }
These rules are applied to initiate the registry. The metrics already END
standardized are identified in the section 5 'IPPM 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 the metrics standardized in future RFC 4.2. Initial IPPM metrics registry
The specification of metrics is a continuous process. The same rules are Metrics specified in a RFC of the WG IPPM are registered in the node
applied to number the metrics of the new RFC. The identifiers are rfc(1). They are numbered using the RFC order and the metrics
included in the section 'Standard metrics registry' of the RFC. definitions order in each memo. The value assigned to a metric is
definitive and cannot be reused.
The status of the identifiers assigned previously to the draft These rules are applied to create the first IPPM the registry. The
corresponding to the new RFC are set up to 'obsolete' and may not be metrics already standardized are registered in the section named
reassigned. 'IPPM metrics registry' of this memo.
4.3. Metrics specified in a WG draft 4.3. IPPM registry management
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
to provide temporary metric identifiers to facilitate software need to provide temporary metric identifiers to facilitate software
integration and to permit interoperability measurement among different integration and to permit interoperability measurement among
implementations. Otherwise the interoperability will be extremely different implementations. Otherwise the interoperability will be
limited du to the fact that implementers will choose arbitrary values to extremely limited du to the fact that implementers will choose
identify the new metrics. arbitrary values to identify the new metrics.
4.3.1. Rules
The metrics specified in an IPPM draft are registered in the node
draft(2).
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
numbered the metrics because usually the metric name does not change
among the different releases. On the other hand new metrics may be added
in successive releases of a draft.
4.3.2. Current WG drafts integration in the registry
The current drafts are numbered using the submission orders of their
current release and using the order of the metrics definition in each
memo.
The previous rules are applied to initiate the registry. The metrics
specified in current WG drafts are identified in the section 5 'draft
metrics registry' of this memo. The registry definition should be
respectful of the format defined in "4.1 Metrics registry format".
4.3.3. Identification of a metric added to an existing WG draft
Despite new metrics are rarely created in successive releases of a
draft, an arbitrary metric identifier may be provided by the IPPM WG to
identify the new metric.
The identifier is added in the section named 'Draft metrics registry' of
the draft. The registry definition should be respectful of the format
defined in "4.1 Metrics registry format".
4.3.4. Identification of the metrics defined in future WG drafts
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.
These identifiers are included in the draft in a section named 'Draft
metrics registry'. The registry definition should be respectful of the
format defined in "4.1 Metrics registry format".
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- When the draft is considered mature, that is when all the metrics are
Multicast-Instantaneous-Hop-One-way-Delay. defined and when they names are chosen:
The name of this metric in the section 'Draft metrics registry' is The authors will insert a registry in the section 'Standard
'draftMulticastInstantaneousHopOneWayDelay'. When this draft will go to metrics registry' of their document. A registry template is
RFC, the metric name will become 'multicastInstantaneousHopOneWayDelay'. proposed above.
4.4. Metrics specified in other documents The chairs of the IPPM WG provide metrics identifiers from the
rfc(1) node of the registry.
Other metrics may be associated with identifiers in the sub tree 4.4. Identification of metric from other organization
other(4). The identifiers are provided by the IPPM WG.
These identifiers are included in the corresponding document in a Metrics defined by other organization may be registered in the node
section named 'IPPM registry identifiers'. The registry definition other(2).
should be respectful of the format defined in "4.1 Metrics registry
format".
5. Initial IPPM registry 5. Initial IPPM registry
IPPM-METRICS-REGISTRY DEFINITIONS ::= BEGIN IPPM-METRICS-REGISTRY DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-IDENTITY,
experimental,
MODULE-IDENTITY MODULE-IDENTITY
FROM SNMPv2-SMI; FROM SNMPv2-SMI;
ippmMetricsRegistry MODULE-IDENTITY ippmMetricsRegistry MODULE-IDENTITY
LAST-UPDATED "200206241100Z" -- June 24, 2002 LAST-UPDATED "200303011100Z" -- March 1st, 2003
ORGANIZATION "IPPM working Group" ORGANIZATION "IPPM working Group"
CONTACT-INFO "ippm@advanced.org" CONTACT-INFO "ippm@advanced.org"
DESCRIPTION DESCRIPTION
" This memo defines a portion of the Management Information Base " This memo defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP-based (MIB) for use with network management protocols in TCP/IP-based
internets. In particular, it defines a registry of the IPPM working internets. In particular, it defines a registry of the IPPM
group metrics." working group metrics."
REVISION "200206241100z" REVISION "200303011100Z"
DESCRIPTION
"Registration rules simplified: see section change since 01."
REVISION "200206241100Z"
DESCRIPTION DESCRIPTION
"Each metric identifier is defined in a OBJECT IDENTITY macro." "Each metric identifier is defined in a OBJECT IDENTITY macro."
::= { ippm 1 } ::= { experimental 10002 }
--
-- ippm OBJECT IDENTIFIER ::= XXXX -- To be assigned
--
rfc OBJECT IDENTIFIER ::= { registry 1 } rfc OBJECT IDENTIFIER ::= { ippmMetricsRegistry 1 }
draft OBJECT IDENTIFIER ::= { registry 2 } other OBJECT IDENTIFIER ::= { ippmMetricsRegistry 2 }
other OBJECT IDENTIFIER ::= { registry 4 }
-- --
-- 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"
-- --
instantaneousUnidirectionalConnectivity OBJECT-IDENTITY instantUnidirectionConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Instantaneous-Unidirectional- "The identifier for the Type-P-Instantaneous-Unidirectional-
Connectivity metric." Connectivity metric."
REFERENCE "RFC2678, section 2." REFERENCE "RFC2678, section 2."
::={rfc 1} ::={rfc 1}
instantaneousBidirectionalConnectivity OBJECT-IDENTITY instantBidirectionConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Instantaneous-Bidirectional- "The identifier for the Type-P-Instantaneous-Bidirectional-
Connectivity metric." Connectivity metric."
REFERENCE "RFC2678, section 3." REFERENCE "RFC2678, section 3."
::={rfc 2} ::={rfc 2}
intervalUnidirectionalConnectivity OBJECT-IDENTITY intervalUnidirectionConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Interval-Unidirectional- "The identifier for the Type-P-Interval-Unidirectional-
Connectivity metric." Connectivity metric."
REFERENCE "RFC2678, section 4." REFERENCE "RFC2678, section 4."
::= { rfc 3 } ::= { rfc 3 }
intervalBidirectionalConnectivity OBJECT-IDENTITY intervalBidirectionConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Interval-Bidirectional- "The identifier for the Type-P-Interval-Bidirectional-
Connectivity metric." Connectivity metric."
REFERENCE "RFC2678, section 5." REFERENCE "RFC2678, section 5."
::= { rfc 4 } ::= { rfc 4 }
intervalTemporalConnectivity OBJECT-IDENTITY intervalTemporalConnectivity OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P1-P2-Interval-Temporal- "The identifier for the Type-P1-P2-Interval-Temporal-
Connectivity metric. " Connectivity metric. "
REFERENCE "RFC2678, section 6." REFERENCE "RFC2678, section 6."
Type-P-One-way-Delay
::= { rfc 5 } ::= { rfc 5 }
-- --
-- RFC 2679 "A One-way Delay Metric for IPPM" -- RFC 2679 "A One-way Delay Metric for IPPM"
-- --
oneWayDelay OBJECT-IDENTITY oneWayDelay OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-One-way-Delay metric. " "The identifier for the Type-P-One-way-Delay metric. "
skipping to change at page 9, line 42 skipping to change at page 8, line 50
roundtripDelayInversePercentile OBJECT-IDENTITY roundtripDelayInversePercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier for the Type-P-Round-trip-Inverse-Percentile "The identifier for the Type-P-Round-trip-Inverse-Percentile
metric." metric."
REFERENCE "RFC2681, section 4.4." REFERENCE "RFC2681, section 4.4."
::= { rfc 20 } ::= { rfc 20 }
-- --
-- Registry of the metrics of the IPPM WG drafts -- RFC3357: "One-way Loss Pattern Sample Metrics"
--
--
-- One-way Loss Pattern Sample Metrics draft
-- --
draftOneWayLossDistanceStream OBJECT-IDENTITY oneWayLossDistanceStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-Way-Loss-Distance- "The identifier for the Type-P-One-Way-Loss-Distance-Stream
Stream metric." metric."
REFERENCE "Work in progress" REFERENCE " RFC3357, section 5.4.1."
::={draft 1} ::={ rfc 21}
draftOneWayLossPeriodStream OBJECT-IDENTITY oneWayLossPeriodStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-Way-Loss-Period-Stream "The identifier for the Type-P-One-Way-Loss-Period-Stream
metric." metric."
REFERENCE "Work in progress" REFERENCE " RFC3357, section 5.4.2."
::={draft 2} ::={ rfc 22}
draftOneWayLossNoticeableRate OBJECT-IDENTITY oneWayLossNoticeableRate OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-Way-Loss-Noticeable- "The identifier for the Type-P-One-Way-Loss-Noticeable-Rate
Rate metric." metric."
REFERENCE "Work in progress" REFERENCE " RFC3357, section 6.1."
::= { draft 3 } ::= { rfc 23 }
draftOneWayLossPeriodTotal OBJECT-IDENTITY oneWayLossPeriodTotal OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-Way-Loss-Period-Total "The identifier for the Type-P-One-Way-Loss-Period-Total
metric." metric."
REFERENCE "Work in progress" REFERENCE " RFC3357, section 6.2."
::= { draft 4 } ::= { rfc 24 }
draftOneWayLossPeriodLengths OBJECT-IDENTITY oneWayLossPeriodLengths OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-Way-Loss-Period-Lengths "The identifier for the Type-P-One-Way-Loss-Period-Lengths
metric." metric."
REFERENCE "Work in progress" REFERENCE " RFC3357, section 6.3."
::= { draft 5 } ::= { rfc 25 }
draftOneWayInterLossPeriodLengths OBJECT-IDENTITY oneWayInterLossPeriodLengths OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-Way-Inter-Loss-Period- "The identifier for the Type-P-One-Way-Inter-Loss-Period-Lengths
Lengths metric." metric."
REFERENCE "Work in progress" REFERENCE " RFC3357, section 6.4."
::= { draft 6 } ::= { rfc 26 }
-- --
-- Network performance measurement with periodic streams draft -- RFC3393: "IP Packet Delay Variation Metric for IP Performance
Metrics (IPPM)"
-- --
oneWayIpdv OBJECT-IDENTITY
draftOneWayDelayPeriodicStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-way-Delay-Periodic- "The identifier for the Type-P-One-way-ipdv metric."
Stream metric." REFERENCE " RFC3393, section 2."
REFERENCE "Work in progress" ::= { rfc 27 }
::= { draft 7 }
--
-- IP Packet Delay Variation Metrics draft
--
draftOneWayIpdv OBJECT-IDENTITY oneWayIpdvPoissonStream OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-way-ipdv metric." "The identifier for the Type-P-One-way-ipdv-Poisson-stream
REFERENCE "Work in progress" metric."
::= { draft 8 } REFERENCE " RFC3393, section 3."
::= { rfc 28 }
draftOneWayIpdvPoissonStream OBJECT-IDENTITY oneWayIpdvPercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-way-ipdv-Poisson-stream "The identifier for the Type-P-One-way-ipdv-percentile metric."
metric." REFERENCE " RFC3393, section 4.3."
REFERENCE "Work in progress" ::= { rfc 29 }
::= { draft 9 }
draftOneWayIpdvPercentile OBJECT-IDENTITY oneWayIpdvInversePercentile OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-way-ipdv-percentile "The identifier for the Type-P-One-way-ipdv-inverse-percentile
metric." metric."
REFERENCE "Work in progress" REFERENCE " RFC3393, section 4.4."
::= { draft 10 } ::= { rfc 30 }
draftOneWayIpdvJitter OBJECT-IDENTITY oneWayIpdvJitter OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-way-ipdv-jitter "The identifier for the Type-P-One-way-ipdv-jitter metric."
metric." REFERENCE " RFC3393, section 4.5."
REFERENCE "Work in progress" ::= { rfc 31 }
::= { draft 11 }
draftOneWayPeakToPeakIpdv OBJECT-IDENTITY oneWayPeakToPeakIpdv OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The draft identifier for the Type-P-One-way-peak-to-peak-ipdv "The identifier for the Type-P-One-way-peak-to-peak-ipdv
metric." metric."
REFERENCE "Work in progress" REFERENCE " RFC3393, section 4.6."
::= { draft 12 } ::= { rfc 32 }
-- --
-- Metrics registry from other documents -- RFC3432: "Network performance measurement with periodic streams"
-- --
oneWayDelayPeriodicStream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The identifier for the Type-P-One-way-Delay-Periodic-Stream
metric."
REFERENCE " RFC3432, section 4."
::= { rfc 33 }
END END
6. References 6. Change since release 00
Macro OBJECT-IDENTITY used to identify the metrics
7. Change since release 01
+ Registrations rules simplified;
+ Draft sub tree removed;
+ Loss pattern metrics of the RFC3357 added to the registry.
+ ipdv metrics of the RFC3393 added to the registry.
+ Periodic streams metrics of the RFC3432 added to the registry.
56th IETF open issues:
should metrics OID be 8 bytes length ? Y/N
-- should be ::= { ippm 1 }
-- with ippm OBJECT IDENTIFIER ::= { mgmt xxx }
-- to have metrics OID to be 8 bytes length.
-- 1.3.6.1.2.ippm.ippmMetricRegistry.rfc.oneWayDelay
8. References
[1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP [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
Loss Metric for IPPM", RFC 2680, September 1999. Loss Metric for IPPM", RFC 2680, September 1999.
[5]Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip Delay [5]Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip Delay
Metric for IPPM.", RFC 2681, September 1999. Metric for IPPM.", RFC 2681, September 1999.
7. Author's Addresses 9. Author's Addresses
Emile STEPHAN Emile STEPHAN
France Telecom R & D France Telecom R & D
2 avenue Pierre Marzin 2 avenue Pierre Marzin
F-22307 Lannion cedex F-22307 Lannion cedex
Phone: (+ 33) 2 96 05 11 11 Phone: (+ 33) 2 96 05 11 11
Email: emile.stephan@francetelecom.com Email: emile.stephan@francetelecom.com
Full Copyright Statement Full Copyright Statement
 End of changes. 

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