draft-ietf-xrblock-rtcp-xr-decodability-02.txt   draft-ietf-xrblock-rtcp-xr-decodability-03.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: April 25, 2013 H. Asaeda Expires: June 20, 2013 H. Asaeda
NICT NICT
G. Zorn, Ed. G. Zorn, Ed.
Network Zen Network Zen
October 22, 2012 December 17, 2012
RTP Control Protocol (RTCP) Extended Report (XR) Block for TS RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG
Decodability Statistics Metric reporting Transport Stream Decodability Statistics Metric reporting
draft-ietf-xrblock-rtcp-xr-decodability-02 draft-ietf-xrblock-rtcp-xr-decodability-03
Abstract Abstract
Transport Stream (TS) is a standard container format used in the An MPEG Transport Stream (TS) is a standard container format used in
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 decodability statistics metrics Block that allows the reporting of MPEG Transport Stream decodability
related to transmissions of MPEG-TS over RTP. 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 April 25, 2013. This Internet-Draft will expire on June 20, 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
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. MPEG Transport Stream Decodability Metrics . . . . . . . . 3
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
3. TR 101 290 Decodability Statistics Metric Report Block . . . . 3 1.3. Performance Metrics Framework . . . . . . . . . . . . . . . 3
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. SDP rtcp-xr-attrib Atrribute Extension . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 6 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 3. MPEG Transport Stream Decodability Statistics Metric
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 Report Block . . . . . . . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1. SDP rtcp-xr-attrib Atrribute Extension . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . . 7 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
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 draft 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
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 occurances of each indicator in supports reporting of the number of occurrences of each indicator in
the first and second priorities; third priority indicators are not the first and second priorities; third priority indicators are not
supported. This new block type can be useful for measuring content supported.
stream or TS quality by checking TS header information [ETSI] and
identifying the existence, and characterizing the severity, of 1.2. RTCP and RTCP XR Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defined an extensible structure for reporting using an RTCP Extended
Report (XR). This document defines a new Extended Report block for
use with [RFC3550] and [RFC3611].
1.3. Performance Metrics Framework
The Performance Metrics Framework [RFC6390] provides guidance on the
definition and specification of performance metrics. The RTP
Monitoring Architectures [RFC6792] provides guideline for reporting
block format using RTCP XR. The new report block described in this
memo is in compliance with the monitoring architecture specified in
[RFC6792] and the Performance Metrics Framework [RFC6390].
1.4. Applicability
These metrics are applicable to any type of RTP application that uses
the MPEG-TS standard format for multimedia data; for example, MPEG4
TS content over RTP. This new block type can be useful for measuring
content stream or TS quality by checking TS header information [ETSI]
and identifying the existence, and characterizing the severity, of
bitstream packetization problems which may affect users' perception bitstream packetization problems which may affect users' perception
of a service delivered over RTP; it may also be useful for verifying of a service delivered over RTP; it may also be useful for verifying
the continued correct operation of an existing system management the continued correct operation of an existing system management
tool. tool.
The new report block is in compliance with the monitoring
architecture specified in Wu, et al. [MONARCH] and the Performance
Metrics Framework [RFC6390]. The metric is applicable to any type of
RTP application that uses the TS standard format for multimedia data;
for example, MPEG4 TS content over RTP.
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. TR 101 290 Decodability Statistics Metric Report Block 3. MPEG Transport Stream Decodability Statistics Metric Report Block
This block reports decodability statistics metrics beyond the This block reports MPEG transport stream decodability statistics
information carried in the standard RTCP packet format. It defines metrics beyond the information carried in the standard RTCP packet
eight metrics based on ETSI TR 101 290. Information is reported format, which are measured at the receiving end of the RTP stream.
about basic monitoring parameters necessary to ensure that the TS can It defines eight metrics based on ETSI TR 101 290. Information is
be decoded including: reported about basic monitoring parameters necessary to ensure 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 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 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 Decodability Metrics Block has the following format: The MPEG-TS 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=TBD | Reserved | block length | | BT=TSDM | Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq | | begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of TSs | | Number of TSs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TS_sync_loss_count | | TS_sync_loss_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sync_byte_error_count | | Sync_byte_error_count |
skipping to change at page 5, line 7 skipping to change at page 5, line 35
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR_repetition_error_count | | PCR_repetition_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR_discontinuity_indicator_error_count | | PCR_discontinuity_indicator_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PTS_error_count | | PTS_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
block type (BT): 8 bits block type (BT): 8 bits
A TR 101 290 decodability metrics report block is identified by A TR 101 290 MPEG-TS decodability metrics report block is
the constant <TDM>. identified by the constant <TSDM>.
Reserved: 8 bits Reserved: 8 bits
This field is reserved for future definition. In the absence of This field is reserved for future definition. In the absence of
such a definition, the bits in this field MUST be set to zero and such a definition, the bits in this field MUST be set to zero and
SHOULD be ignored by the receiver. 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 11, in accordance with the definition of this field
in Section 3 of RFC 3611. in Section 3 of RFC 3611. The block MUST be discarded if the
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.
end_seq: 16 bits end_seq: 16 bits
As defined in Section 4.1 of RFC 3611. As defined in Section 4.1 of RFC 3611.
Number of TSs: 32 bits Number of TSs: 32 bits
Number of TS in the above sequence number interval. Number of TS in the above sequence number interval.
TS_sync_loss_count: 32 bits TS_sync_loss_count: 32 bits
Number of TS_sync_loss errors in the above sequence number Number of TS_sync_loss errors in the above sequence number
interval. interval. It is calculated based on the occurrence of errors for
"TS_sync_loss"parameter defined in the table 5.2.1 of ETSI TR 101
290 (See section 5.5.1 of ETSI TR 101 290).
Sync_byte_error_count: 32 bits Sync_byte_error_count: 32 bits
Number of sync_byte_errors in the above sequence number interval. Number of sync_byte_errors in the above sequence number interval.
It is calculated in the same way as TS_sync_loss_count, i.e.,based
on the occurrence of errors for "Sync_byte_error"parameter defined
in the table 5.2.1 of ETSI TR 101 290.
Continuity_count_error_count: 32 bits Continuity_count_error_count: 32 bits
Number of Continuity_count_errors in the above sequence number Number of Continuity_count_errors in the above sequence number
interval. interval. Simiarly, it is calculated based on the occurrence of
errors for "Continuity_count_error"parameter defined in the table
5.2.1 of ETSI TR 101 290.
Transport_error_count: 32 bits Transport_error_count: 32 bits
Number of Transport_errors in the above sequence number interval. Number of Transport_errors in the above sequence number interval.
Simiarly, it is calculated based on the occurrence of errors for
"Transport_error" parameter defined in the table 5.2.2 of ETSI TR
101 290.
PCR_error_count: 32 bits PCR_error_count: 32 bits
Number of PCR_errors in the above sequence number interval. Number of PCR_errors in the above sequence number interval.
Simiarly, it is calculated based on the occurrence of errors for
"PCR_error"parameter defined in the table 5.2.2 of ETSI TR 101
290.
PCR_repetition_error_count: 32 bits PCR_repetition_error_count: 32 bits
Number of PCR_repetition_errors in the above sequence number Number of PCR_repetition_errors in the above sequence number
interval. interval. Simiarly, it is calculated based on the occurrence of
errors for "PCR_repetition_error"parameter defined in the table
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. number interval. Simiarly, it is calculated based on the
occurrence of errors for
"PCR_discontinuity_indicator_error"parameter defined in the table
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
"PTS_error"parameter defined in the table 5.2.2 of ETSI TR 101
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. XR blocks MAY be [RFC4566] for signaling the use of RTCP XR blocks. XR blocks MAY be
used without prior signaling. used without prior signaling.
4.1. SDP rtcp-xr-attrib Atrribute Extension 4.1. SDP rtcp-xr-attrib Atrribute 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 =/ decodability-metrics xr-format =/ ts-decodability-metrics
decodability-metrics = "decodability-metrics" ts-decodability-metrics = "ts-decodability-metrics"
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 RFC 3611 applies. defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters
applies. For detailed usage in Offer/Answer for unilateral
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 RTCP XR Block This document assigns one new block type value in the RTCP XR Block
Type Registry: Type Registry:
Name: TDM Name: TSDM
Long Name: TR 101 290 Decodability Metrics Long Name: TR 101 290 MPEG Transport Stream Decodability Metrics
Value <TDM> Value <TSDM>
Reference: Section 3 Reference: Section 3
This document also registers one SDP [RFC4566] parameters for the This document also registers one SDP [RFC4566] parameters for the
"rtcp-xr" attribute in the RTCP XR SDP Parameter Registry: "rtcp-xr" attribute in the RTCP XR SDP Parameter Registry:
* "decodability-metrics" * "ts-decodability-metrics"
The contact information for the registrations is: The contact information for the registrations is:
Rachel Huang Qin Wu
rachel.huang@huawei.com sunseawq@huawei.com
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, JiangSu 210012 China 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 for useful review and suggestions. Thanks to Ray van Brandenburg, Claire Bi,Colin Perkin and Dan
Romascanufor useful review and suggestions.
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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
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.
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.
[MONARCH] Wu, Q., Hunt, G., and P. , "Monitoring Architectures for
RTP", ID draft-ietf-avtcore-monarch-22, September 2012.
[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,
October 2011. October 2011.
[RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the
RTP Monitoring Framework", RFC 6792, November 2012.
Authors' Addresses Authors' Addresses
Rachel Huang Rachel Huang
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing 210012 Nanjing 210012
China China
Email: rachel.huang@huawei.com Email: rachel.huang@huawei.com
Qin Wu Qin Wu
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: bill.wu@huawei.com Email: bill.wu@huawei.com
Hitoshi Asaeda Hitoshi Asaeda
National Institute of Information and Communications Technology National Institute of Information and Communications Technology
4-2-1 Nukui-Kitamachi 4-2-1 Nukui-Kitamachi
Koganei, Tokyo 184-8795 Koganei, Tokyo 184-8795
Japan Japan
Email: asaeda@nict.go.jp Email: asaeda@nict.go.jp
Glen Zorn (editor) Glen Zorn (editor)
Network Zen Network Zen
 End of changes. 39 change blocks. 
64 lines changed or deleted 115 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/