draft-ietf-xrblock-rtcp-xr-decodability-04.txt   draft-ietf-xrblock-rtcp-xr-decodability-05.txt 
Network Working Group R. Huang Network Working Group R. Huang
Internet-Draft Q. Wu Internet-Draft Q. Wu
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: June 21, 2013 H. Asaeda Expires: June 24, 2013 H. Asaeda
NICT NICT
G. Zorn, Ed. G. Zorn, Ed.
Network Zen Network Zen
December 18, 2012 December 21, 2012
RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG
Transport Stream Decodability Statistics Metric reporting Transport Stream (TS) Program Specific Information (PSI) Independent
draft-ietf-xrblock-rtcp-xr-decodability-04 Decodability Statistics Metric reporting
draft-ietf-xrblock-rtcp-xr-decodability-05
Abstract Abstract
An MPEG Transport Stream (TS) is a standard container format used in An MPEG Transport Stream (TS) is a standard container format used in
the transmission and storage of multimedia data. Unicast/Multicast/ the transmission and storage of multimedia data. Unicast/Multicast/
Broadcast MPEG-TS over RTP is widely deployed in IPTV systems. This Broadcast MPEG-TS over RTP is widely deployed in IPTV systems. This
document defines an RTP Control Protocol (RTCP) Extended Report (XR) document defines an RTP Control Protocol (RTCP) Extended Report (XR)
Block that allows the reporting of MPEG Transport Stream decodability Block that allows the reporting of MPEG TS Program Specific
statistics metrics related to transmissions of MPEG-TS over RTP. Information (PSI) Independent decodability statistics metrics related
to transmissions of MPEG-TS over RTP.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on June 21, 2013. This Internet-Draft will expire on June 24, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. MPEG Transport Stream Decodability Metrics . . . . . . . . 3 1.1. MPEG Transport Stream Decodability Metrics . . . . . . . . 3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . . 3 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . . 3 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
3. MPEG Transport Stream Decodability Statistics Metric 3. MPEG TS PSI Independent Decodability Statistics Metric
Report Block . . . . . . . . . . . . . . . . . . . . . . . . . 4 Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. SDP rtcp-xr-attrib Atrribute Extension . . . . . . . . . . 7 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 7
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.3. Contact information for registrations . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . . 9 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
1.1. MPEG Transport Stream Decodability Metrics 1.1. MPEG Transport Stream Decodability Metrics
The European Telecommunications Standards Institute (ETSI) has The European Telecommunications Standards Institute (ETSI) has
defined a set of syntax and information consistency tests and defined a set of syntax and information consistency tests and
corresponding indicators [ETSI] that are recommended for the corresponding indicators [ETSI] that are recommended for the
monitoring of MPEG-2 Transport Streams [ISO-IEC.13818-1.2007]. The monitoring of MPEG-2 Transport Streams [ISO-IEC.13818-1.2007]. The
tests and corresponding indicators are grouped according to priority: tests and corresponding indicators are grouped according to priority:
o First priority - Necessary for de-codability (basic monitoring) o First priority - Necessary for de-codability (basic monitoring)
o Second priority - Recommended for continuous or periodic o Second priority - Recommended for continuous or periodic
monitoring monitoring
o Third priority - Recommended for application-dependant monitoring o Third priority - Recommended for application-dependant monitoring
This memo is based on information consistency tests and resulting This memo is based on information consistency tests and resulting
indicators defined by ETSI [ETSI] and defines a new block type to indicators defined by ETSI [ETSI] and defines a new block type to
augment those defined in Freidman, et al. [RFC3611] for use with augment those defined in Freidman, et al. [RFC3611] for use with MPEG
Transport Stream (TS) [ISO-IEC.13818-1.2007]. The new block type Transport Stream (TS) [ISO-IEC.13818-1.2007]. The new block type
supports reporting of the number of occurrences of each indicator in supports reporting of the number of occurrences of each Program
the first and second priorities; third priority indicators are not Specific Information (PSI) Independent indicator in the first and
supported. second priorities; third priority indicators are not supported.
1.2. RTCP and RTCP XR Reports 1.2. RTCP and RTCP XR Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defined an extensible structure for reporting using an RTCP Extended defined an extensible structure for reporting using an RTCP Extended
Report (XR). This document defines a new Extended Report block for Report (XR). This document defines a new Extended Report block for
use with [RFC3550] and [RFC3611]. use with [RFC3550] and [RFC3611].
1.3. Performance Metrics Framework 1.3. Performance Metrics Framework
skipping to change at page 4, line 15 skipping to change at page 4, line 15
tool. tool.
2. Terminology 2. Terminology
2.1. Standards Language 2.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. MPEG Transport Stream Decodability Statistics Metric Report Block 3. MPEG TS PSI Independent Decodability Statistics Metric Block
This block reports MPEG transport stream decodability statistics This block reports MPEG TS PSI Independent decodability statistics
metrics beyond the information carried in the standard RTCP packet metrics beyond the information carried in the standard RTCP packet
format, which are measured at the receiving end of the RTP stream. format, which are measured at the receiving end of the RTP stream.
It defines eight metrics based on ETSI TR 101 290. Information is It describes eight metrics specified in ETSI TR 101 290. Information
reported about basic monitoring parameters necessary to ensure that is reported about basic monitoring parameters necessary to ensure
the TS can be decoded including: that the TS can be decoded including:
o Transport Stream Synchronization Losses o Transport Stream Synchronization Losses
o Sync byte errors o Sync byte errors
o Continuity count errors o Continuity count errors
and continuous monitoring parameters including: and continuous monitoring parameters necessary to ensure the
continuous decoding including:
o Transport errors o Transport errors
o Program Clock Reference (PCR) errors o Program Clock Reference (PCR) errors
o PCR repetition errors o PCR repetition errors
o PCR discontinuity indicator errors o PCR discontinuity indicator errors
o PCR accuracy errors
o Presentation Time Stamp (PTS) errors o Presentation Time Stamp (PTS) errors
The other parameters are ignored since they do not apply to all MPEG The other parameters are ignored since they do not apply to all MPEG
implementations. For further information on these parameters, see implementations. For further information on these parameters, see
[ETSI]. [ETSI].
The MPEG-TS Decodability Metrics Block has the following format: The MPEG-TS PSI Independent Decodability Metrics Block has the
following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=TSDM | Reserved | block length | | BT=TSDM | Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq | | begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 30 skipping to change at page 5, line 30
| Continuity_count_error_count | | Continuity_count_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transport_error_count | | Transport_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR_error_count | | PCR_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR_repetition_error_count | | PCR_repetition_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR_discontinuity_indicator_error_count | | PCR_discontinuity_indicator_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR_accuracy_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PTS_error_count | | PTS_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
block type (BT): 8 bits block type (BT): 8 bits
A TR 101 290 MPEG-TS decodability metrics report block is The MPEG-TS PSI Independent Decodability Metrics Block is
identified by the constant <TSDM>. identified by the constant <MPID>.
Reserved: 8 bits Reserved: 8 bits
This field is reserved for future definition. In the absence of These bits are reserved. They MUST be set to zero by senders
such a definition, the bits in this field MUST be set to zero and ignored by receivers (See [RFC6709] section 4.2).
SHOULD be ignored by the receiver.
block length: 16 bits block length: 16 bits
The constant 11, in accordance with the definition of this field The constant 12, in accordance with the definition of this field
in Section 3 of RFC 3611. The block MUST be discarded if the in Section 3 of RFC 3611. The block MUST be discarded if the
block length is set to a different value. block length is set to a different value.
SSRC of source: 32 bits SSRC of source: 32 bits
As defined in Section 4.1 of RFC 3611. As defined in Section 4.1 of RFC 3611.
begin_seq: 16 bits begin_seq: 16 bits
As defined in Section 4.1 of RFC 3611. As defined in Section 4.1 of RFC 3611.
skipping to change at page 7, line 27 skipping to change at page 7, line 27
5.2.2 of ETSI TR 101 290. 5.2.2 of ETSI TR 101 290.
PCR_discontinuity_indicator_error_count: 32 bits PCR_discontinuity_indicator_error_count: 32 bits
Number of PCR_discontinuity_indicator_errors in the above sequence Number of PCR_discontinuity_indicator_errors in the above sequence
number interval. Simiarly, it is calculated based on the number interval. Simiarly, it is calculated based on the
occurrence of errors for occurrence of errors for
"PCR_discontinuity_indicator_error"parameter defined in the "PCR_discontinuity_indicator_error"parameter defined in the
section 5.2.2 of ETSI TR 101 290. section 5.2.2 of ETSI TR 101 290.
PCR_error_count: 32 bits
Number of PCR_accuracy_errors in the above sequence number
interval. Simiarly, it is calculated based on the occurrence of
errors for "PCR_accuracy_error"parameter defined in the section
5.2.2 of ETSI TR 101 290.
PTS_error_count: 32 bits PTS_error_count: 32 bits
Number of PTS_errors in the above sequence number interval. Number of PTS_errors in the above sequence number interval.
Simiarly, it is calculated based on the occurrence of errors for Simiarly, it is calculated based on the occurrence of errors for
"PTS_error"parameter defined in the section 5.2.2 of ETSI TR 101 "PTS_error"parameter defined in the section 5.2.2 of ETSI TR 101
290. 290.
4. SDP Signaling 4. SDP Signaling
RFC 3611 defines the use of SDP (Session Description Protocol) RFC 3611 defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of RTCP XR blocks. However XR blocks [RFC4566] for signaling the use of RTCP XR blocks. However XR blocks
MAY be used without prior signaling (See section 5 of RFC3611). MAY be used without prior signaling (See section 5 of RFC3611).
4.1. SDP rtcp-xr-attrib Atrribute Extension 4.1. SDP rtcp-xr-attrib Attribute Extension
This session augments the SDP attribute "rtcp-xr" defined in Section This session augments the SDP attribute "rtcp-xr" defined in Section
5.1 of RFC 3611 by providing an additional value of "xr-format" to 5.1 of RFC 3611 by providing an additional value of "xr-format" to
signal the use of the report block defined in this document. signal the use of the report block defined in this document.
xr-format =/ ts-decodability-metrics xr-format =/ xr-nptd-block
ts-decodability-metrics = "ts-decodability-metrics" xr-nptd-block = "non-psi-ts-decodability"
4.2. Offer/Answer Usage 4.2. Offer/Answer Usage
When SDP is used in offer-answer context, the SDP Offer/Answer usage When SDP is used in offer-answer context, the SDP Offer/Answer usage
defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters
applies. For detailed usage of Offer/Answer for unilateral applies. For detailed usage of Offer/Answer for unilateral
parameter, refer to section 5.2 of [RFC3611]. parameter, refer to section 5.2 of [RFC3611].
5. IANA Considerations 5. IANA Considerations
New report block types for RTCP XR are subject to IANA registration. New report block types for RTCP XR are subject to IANA registration.
For general guidelines on IANA allocations for RTCP XR, refer to For general guidelines on IANA allocations for RTCP XR, refer to
Section 6.2 ofRFC 3611. Section 6.2 ofRFC 3611.
This document assigns one new block type value in the "RTP Control 5.1. New RTCP XR Block Type value
Protocol Extended Reports (RTCP XR) Block Type Registry " Registry:
Name: TSDM This document assigns the block type value MPID in the IANA " RTP
Long Name: TR 101 290 MPEG Transport Stream Decodability Metrics Control Protocol Extended Reports (RTCP XR) Block Type Registry " to
Value <TSDM> the " MPEG Transport Stream PSI Independent Decodability Statistics
Reference: Section 3 Metric Block".
This document also registers one SDP [RFC4566] parameters for the [Note to RFC Editor: please replace MPID with the IANA provided RTCP
"rtcp-xr" attribute in the "RTP Control Protocol Extended Reports XR block type for this block.]
(RTCP XR) Session Description Protocol (SDP) Parameters Registry":
* "ts-decodability-metrics" 5.2. New RTCP XR SDP Parameter
The contact information for the registrations is: This document also registers a new parameter " non-psi-ts-
decodability " in the "RTP Control Protocol Extended Reports (RTCP
XR) Session Description Protocol (SDP) Parameters Registry".
Qin Wu 5.3. Contact information for registrations
sunseawq@huawei.com
101 Software Avenue, Yuhua District The contact information for the registrations is:
Nanjing, JiangSu 210012 China
6. Security Considerations 6. Security Considerations
This proposed RTCP XR report block introduces no new security This proposed RTCP XR report block introduces no new security
considerations beyond those described in RFC 3611. considerations beyond those described in RFC 3611.
7. Acknowledgements 7. Acknowledgements
Thanks to Ray van Brandenburg, Claire Bi,Colin Perkin and Dan Thanks to Ray van Brandenburg, Claire Bi,Colin Perkin,Roni Even and
Romascanufor useful review and suggestions. Dan Romascanufor useful review and suggestions.
Qin Wu
sunseawq@huawei.com
101 Software Avenue, Yuhua District
Nanjing, JiangSu 210012 China
8. References 8. References
8.1. Normative References 8.1. Normative References
[ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement
guidelines for DVB systems", Technical Report TR 101 290, guidelines for DVB systems", Technical Report TR 101 290,
2001. 2001.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 9, line 26 skipping to change at page 9, line 36
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
Applications", RFC 3550, July 2003. Applications", RFC 3550, July 2003.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", RFC 3611, Protocol Extended Reports (RTCP XR)", RFC 3611,
November 2003. November 2003.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
[RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design
Considerations for Protocol Extensions", RFC 6709,
September 2012.
8.2. Informative References 8.2. Informative References
[ISO-IEC.13818-1.2007] [ISO-IEC.13818-1.2007]
International Organization for Standardization, International Organization for Standardization,
"Information technology - Generic coding of moving "Information technology - Generic coding of moving
pictures and associated audio information: Systems", pictures and associated audio information: Systems",
ISO International Standard 13818-1, October 2007. ISO International Standard 13818-1, October 2007.
[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
Performance Metric Development", BCP 170, RFC 6390, Performance Metric Development", BCP 170, RFC 6390,
 End of changes. 30 change blocks. 
63 lines changed or deleted 87 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/