draft-ietf-xrblock-rtcp-xr-qoe-09.txt   draft-ietf-xrblock-rtcp-xr-qoe-10.txt 
Network Working Group A. Clark Network Working Group A. Clark
Internet-Draft Telchemy Internet-Draft Telchemy
Intended status: Standards Track Q. Wu Intended status: Standards Track Q. Wu
Expires: December 20, 2013 Huawei Expires: December 26, 2013 Huawei
R. Schott R. Schott
Deutsche Telekom Deutsche Telekom
G. Zorn G. Zorn
Network Zen Network Zen
June 18, 2013 June 24, 2013
RTP Control Protocol (RTCP) Extended Report (XR) Blocks for QoE Metric RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MoS Metric
Reporting Reporting
draft-ietf-xrblock-rtcp-xr-qoe-09 draft-ietf-xrblock-rtcp-xr-qoe-10
Abstract Abstract
This document defines an RTP Control Protocol (RTCP) Extended Report This document defines an RTP Control Protocol (RTCP) Extended Report
(XR) Block including two new segment types and associated SDP (XR) Block including two new segment types and associated SDP
parameters that allow the reporting of QoE metrics for use in a range parameters that allow the reporting of MoS Metrics for use in a range
of RTP applications. of RTP applications.
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 December 20, 2013. This Internet-Draft will expire on December 26, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. QoE Metrics Report Block . . . . . . . . . . . . . . . . . 4 1.1. MoS Metrics Report Block . . . . . . . . . . . . . . . . . 4
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 4 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 4
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 4 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 4
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5
3. QoE Metrics Block . . . . . . . . . . . . . . . . . . . . . . 6 3. MoS Metrics Block . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Metric Block Structure . . . . . . . . . . . . . . . . . . 6 3.1. Metric Block Structure . . . . . . . . . . . . . . . . . . 6
3.2. Definition of Fields in QoE Metrics Block . . . . . . . . 7 3.2. Definition of Fields in MoS Metrics Block . . . . . . . . 7
3.2.1. Single Stream audio/video per SSRC Segment . . . . . 8 3.2.1. Single Stream audio/video per SSRC Segment . . . . . 8
3.2.2. Multi-Channel audio per SSRC Segment . . . . . . . . . 9 3.2.2. Multi-Channel audio per SSRC Segment . . . . . . . . . 9
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 10 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 11 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 11
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 12 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 14 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 14
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 14 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 14
5.3. The SDP calgextmap Attribute . . . . . . . . . . . . . . . 14 5.3. The SDP calgextmap Attribute . . . . . . . . . . . . . . . 14
5.4. New registry of calculation algorithms . . . . . . . . . . 15 5.4. New registry of calculation algorithms . . . . . . . . . . 15
6. Security Considerations . . . . . . . . . . . . . . . . . . . 16 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7. Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 7. Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.1. Normative References . . . . . . . . . . . . . . . . . . . 17 9.1. Normative References . . . . . . . . . . . . . . . . . . . 17
9.2. Informative References . . . . . . . . . . . . . . . . . . 17 9.2. Informative References . . . . . . . . . . . . . . . . . . 17
Appendix A. Example of User Quality of Experience Evaluation Appendix A. Example of User Quality of Experience Evaluation
for video stream . . . . . . . . . . . . . . . . . . 19 for video stream . . . . . . . . . . . . . . . . . . 19
Appendix B. Metrics represented using RFC6390 Template . . . . . 20 Appendix B. Metrics represented using RFC6390 Template . . . . . 20
Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 22 Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 22
C.1. draft-ietf-xrblock-rtcp-xr-qoe-09 . . . . . . . . . . . . 22 C.1. draft-ietf-xrblock-rtcp-xr-qoe-10 . . . . . . . . . . . . 22
C.2. draft-ietf-xrblock-rtcp-xr-qoe-08 . . . . . . . . . . . . 23 C.2. draft-ietf-xrblock-rtcp-xr-qoe-09 . . . . . . . . . . . . 23
C.3. draft-ietf-xrblock-rtcp-xr-qoe-07 . . . . . . . . . . . . 23 C.3. draft-ietf-xrblock-rtcp-xr-qoe-08 . . . . . . . . . . . . 23
C.4. draft-ietf-xrblock-rtcp-xr-qoe-06 . . . . . . . . . . . . 23 C.4. draft-ietf-xrblock-rtcp-xr-qoe-07 . . . . . . . . . . . . 23
C.5. draft-ietf-xrblock-rtcp-xr-qoe-04 . . . . . . . . . . . . 23 C.5. draft-ietf-xrblock-rtcp-xr-qoe-06 . . . . . . . . . . . . 23
C.6. draft-ietf-xrblock-rtcp-xr-qoe-03 . . . . . . . . . . . . 23 C.6. draft-ietf-xrblock-rtcp-xr-qoe-04 . . . . . . . . . . . . 23
C.7. draft-ietf-xrblock-rtcp-xr-qoe-02 . . . . . . . . . . . . 23 C.7. draft-ietf-xrblock-rtcp-xr-qoe-03 . . . . . . . . . . . . 23
C.8. draft-ietf-xrblock-rtcp-xr-qoe-01 . . . . . . . . . . . . 24 C.8. draft-ietf-xrblock-rtcp-xr-qoe-02 . . . . . . . . . . . . 24
C.9. draft-ietf-xrblock-rtcp-xr-qoe-00 . . . . . . . . . . . . 24 C.9. draft-ietf-xrblock-rtcp-xr-qoe-01 . . . . . . . . . . . . 24
C.10. draft-ietf-xrblock-rtcp-xr-qoe-00 . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
1.1. QoE Metrics Report Block 1.1. MoS Metrics Report Block
This document defines a new block type to augment those defined in This document defines a new block type to augment those defined in
[RFC3611], for use in a range of RTP applications. [RFC3611], for use in a range of RTP applications.
The new block type provides information on media quality using one of The new block type provides information on media quality using one of
several standard metrics (i.e.,Mean Opinion Score(MoS)). several standard metrics (i.e.,Mean Opinion Score(MoS)).
The metrics belong to the class of application level metrics defined The metrics belong to the class of application level metrics defined
in [RFC6792]. in [RFC6792].
skipping to change at page 4, line 36 skipping to change at page 4, line 36
The Performance Metrics Framework [RFC6390] provides guidance on the The Performance Metrics Framework [RFC6390] provides guidance on the
definition and specification of performance metrics. The RTP definition and specification of performance metrics. The RTP
Monitoring Architectures [RFC6792] provides guidelines for reporting Monitoring Architectures [RFC6792] provides guidelines for reporting
block format using RTCP XR. The XR block type described in this block format using RTCP XR. The XR block type described in this
document are in accordance with the guidelines in [RFC6390] and document are in accordance with the guidelines in [RFC6390] and
[RFC6792]. [RFC6792].
1.4. Applicability 1.4. Applicability
The QoE Metrics Report Block can be used in any application of RTP The MoS Metrics Report Block can be used in any application of RTP
for which QoE measurement algorithms are defined. for which QoE measurement algorithms are defined.
The factors that affect real-time audio/video application quality can The factors that affect real-time audio/video application quality can
be split into two categories. The first category consists of be split into two categories. The first category consists of
transport-specific factors such as packet loss, delay and jitter transport-specific factors such as packet loss, delay and jitter
(which also translates into losses in the playback buffer). The (which also translates into losses in the playback buffer). The
factors in the second category are application-specific factors that factors in the second category are application-specific factors that
affect real time application (e.g., video) quality. These factors affect real time application (e.g., video) quality. These factors
can be but are not limited to video codec and loss recovery can be but are not limited to video codec and loss recovery
technique, coding bit rate, packetization scheme, and content technique, coding bit rate, packetization scheme, and content
skipping to change at page 5, line 14 skipping to change at page 5, line 14
Quality of Experience (QoE) that may not be captured in the Quality of Experience (QoE) that may not be captured in the
transmission layers or from the RTP layer down. In a typical transmission layers or from the RTP layer down. In a typical
scenario, monitoring of the transmission layers can produce scenario, monitoring of the transmission layers can produce
statistics suggesting that quality is not an issue, such as the fact statistics suggesting that quality is not an issue, such as the fact
that network jitter is not excessive. However, problems may occur in that network jitter is not excessive. However, problems may occur in
the service layers leading to poor subscriber QoE. Therefore the service layers leading to poor subscriber QoE. Therefore
monitoring using only network-level measurements may be insufficient monitoring using only network-level measurements may be insufficient
when application layer media quality is required. when application layer media quality is required.
In order to provide accurate measures of real time media quality when In order to provide accurate measures of real time media quality when
transporting real time media across a network, the QoE Metrics is transporting real time media across a network, the QoE
highly required which can be conveyed in the RTCP XR packets Metrics(e.g.,MoS Metrics) are highly recommended which can be
[RFC3611] and may have the following three benefits: conveyed in the RTCP XR packets [RFC3611] and may have the following
three benefits:
o Tuning the content encoder algorithm to satisfy real time data o Tuning the content encoder algorithm to satisfy real time data
quality requirements. quality requirements.
o Determining which system techniques to use in a given situation o Determining which system techniques to use in a given situation
and when to switch from one technique to another as system and when to switch from one technique to another as system
parameters change. parameters change.
o Verifying the continued correct operation of an existing system. o Verifying the continued correct operation of an existing system.
2. Terminology 2. Terminology
skipping to change at page 6, line 6 skipping to change at page 6, line 6
255.996 with a granularity of 0.0039. S7:8 would represent the 255.996 with a granularity of 0.0039. S7:8 would represent the
range -127.996 to +127.996. 0:16 represents a proper binary range -127.996 to +127.996. 0:16 represents a proper binary
fraction with range fraction with range
0.0 to 1 - 1/65536 = 0.9999847 0.0 to 1 - 1/65536 = 0.9999847
though note that use of flag values at the top of the numeric though note that use of flag values at the top of the numeric
range slightly reduces this upper limit. For example, if the range slightly reduces this upper limit. For example, if the
16- bit values 0xfffe and 0xffff are used as flags for "over- 16- bit values 0xfffe and 0xffff are used as flags for "over-
range" and "unavailable" conditions, a 0:16 quantity has range range" and "unavailable" conditions, a 0:16 quantity has range
0.0 to 1 - 3/65536 = 0.9999542 0.0 to 1 - 3/65536 = 0.9999542
3. QoE Metrics Block 3. MoS Metrics Block
Multimedia application QoE metric is commonly expressed as a MOS Multimedia application MoS Metric is commonly expressed as a MOS
("Mean Opinion Score"), MOS is on a scale from 1 to 5, in which 5 ("Mean Opinion Score"), MOS is on a scale from 1 to 5, in which 5
represents excellent and 1 represents unacceptable. MOS scores are represents excellent and 1 represents unacceptable. MOS scores are
usually obtained using subjective testing or using objective usually obtained using subjective testing or using objective
algorithm. However Subjective testing to estimate the multimedia algorithm. However Subjective testing to estimate the multimedia
quality may be not suitable for measuring the multimedia quality quality may be not suitable for measuring the multimedia quality
since the results may vary from test to test. Therefore using since the results may vary from test to test. Therefore using
objective algorithm to calculate MOS scores is RECOMMENDED. ITU-T objective algorithm to calculate MOS scores is RECOMMENDED. ITU-T
recommendations (e.g., recommendations (e.g., [G.107][G.107.1][P.862][P.862.1][P.862.2]
[G.107][G.107.1][P.862][P.862.1][P.862.2][P.863][P.564][G.1082][P.120
1.1][P.1201.2][P.1202.1][P.1202.2]) define the methodologies for [P.863][P.564][G.1082][P.1201.1][P.1201.2][P.1202.1][P.1202.2])
assessment of the performance of multimedia stream and provides a define the methodologies for assessment of the performance of
method to evaluate QoE estimation algorithms and objective model for multimedia stream and provides a method to evaluate QoE estimation
video and audio. Hence this document recommends vendors and algorithms and objective model for video and audio. Hence this
implementers to use these International Telecommunication Union document recommends vendors and implementers to use these
(ITU)-specified methodologies to measure parameters when possible. International Telecommunication Union (ITU)-specified methodologies
to measure parameters when possible.
This block reports the multimedia application performance or media This block reports the multimedia application performance or media
quality beyond the information carried in the standard RTCP packet quality beyond the information carried in the standard RTCP packet
format. Information is recorded about QoE metric which provides a format. Information is recorded about MoS Metric which provides a
measure that gives a numerical indication of the perceived quality of measure that gives a numerical indication of the perceived quality of
the media received. The measurement of metrics in this block are the media received. The measurement of metrics in this block are
usually made at the receiving end of the RTP stream. Instances of usually made at the receiving end of the RTP stream. Instances of
this Metrics Block refer by Synchronization source (SSRC) to the this Metrics Block refer by Synchronization source (SSRC) to the
separate auxiliary Measurement Information block [RFC6776] which separate auxiliary Measurement Information block [RFC6776] which
describes measurement periods in use (see RFC6776 section 4.2). describes measurement periods in use (see RFC6776 section 4.2).
This Metrics Block relies on the measurement period in the This Metrics Block relies on the measurement period in the
Measurement Information block indicating the span of the report. Measurement Information block indicating the span of the report.
Senders MUST send this block in the same compound RTCP packet as the Senders MUST send this block in the same compound RTCP packet as the
skipping to change at page 6, line 49 skipping to change at page 7, line 4
measurement period is received in the same compound RTCP packet as measurement period is received in the same compound RTCP packet as
this Metrics Block. If not, this Metrics Block MUST be discarded. this Metrics Block. If not, this Metrics Block MUST be discarded.
3.1. Metric Block Structure 3.1. Metric Block Structure
The report block contents are dependent upon a series of flag bits The report block contents are dependent upon a series of flag bits
carried in the first part of the header. Not all parameters need to carried in the first part of the header. Not all parameters need to
be reported in each block. Flags indicate which are and which are be reported in each block. Flags indicate which are and which are
not reported. The fields corresponding to unreported parameters MUST not reported. The fields corresponding to unreported parameters MUST
be present, and MUST be set to zero. The receiver MUST ignore any be present, and MUST be set to zero. The receiver MUST ignore any
QoE Metrics Block with a non-zero value in any field flagged as MoS Metrics Block with a non-zero value in any field flagged as
unreported. The encoding of QoE metrics block payload consists of a unreported. The encoding of MoS Metrics block payload consists of a
series of 32 bit units called segments that describe payload Type, series of 32 bit units called segments that describe payload Type,
MoS algorithm and MoS value. MoS algorithm and MoS value.
The QoE Metrics Block has the following format: The MoS 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=QMB | I | Reserved | Block Length | | BT=MMB | I | Reserved | Block Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Segment 1 | | Segment 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Segment 2 | | Segment 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
.................. ..................
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Segment n | | Segment n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.2. Definition of Fields in QoE Metrics Block 3.2. Definition of Fields in MoS Metrics Block
Block type (BT): 8 bits Block type (BT): 8 bits
The QoE Metrics Block is identified by the constant <QMB>. The MoS Metrics Block is identified by the constant <MMB>.
Interval Metric flag (I): 2 bits Interval Metric flag (I): 2 bits
This field is used to indicate whether the QoE metrics are This field is used to indicate whether the MoS Metrics are
Sampled, Interval or Cumulative metrics [RFC6792]: Sampled, Interval or Cumulative metrics [RFC6792]:
I=10: Interval Duration - the reported value applies to the I=10: Interval Duration - the reported value applies to the
most recent measurement interval duration between successive most recent measurement interval duration between successive
metrics reports. metrics reports.
I=11: Cumulative Duration - the reported value applies to the I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements. accumulation period characteristic of cumulative measurements.
I=01: Sampled Value - the reported value is a sampled I=01: Sampled Value - the reported value is a sampled
instantaneous value. instantaneous value.
skipping to change at page 8, line 14 skipping to change at page 8, line 14
Reserved: 6 bits Reserved: 6 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
ignored by the receiver (See RFC6709 section 4.2). ignored by the receiver (See RFC6709 section 4.2).
Block Length: 16 bits Block Length: 16 bits
The length of this report block in 32-bit words, minus one. For The length of this report block in 32-bit words, minus one. For
the QoE Metrics Block, the block length is variable length. the MoS Metrics Block, the block length is variable length.
SSRC of source: 32 bits SSRC of source: 32 bits
As defined in Section 4.1 of [RFC3611]. As defined in Section 4.1 of [RFC3611].
Segment i: 32 bits Segment i: 32 bits
There are two segment types defined in this document: single There are two segment types defined in this document: single
stream Audio/Video per SSRC segment, multi-channel audio per SSRC stream Audio/Video per SSRC segment, multi-channel audio per SSRC
segment. Multi-channel audio per SSRC segment is used to deal segment. Multi-channel audio per SSRC segment is used to deal
skipping to change at page 8, line 51 skipping to change at page 8, line 51
This field is used to identify the segment type used in this This field is used to identify the segment type used in this
report block. A zero identifies this as a single stream Audio/ report block. A zero identifies this as a single stream Audio/
Video per SSRC segment. Single stream means there is only one Video per SSRC segment. Single stream means there is only one
media stream carried in one RTP stream. The single stream Audio/ media stream carried in one RTP stream. The single stream Audio/
Video per SSRC segment can be used to report the MoS value Video per SSRC segment can be used to report the MoS value
associated with the media stream identified by SSRC. If there are associated with the media stream identified by SSRC. If there are
multiple media streams and they want to use the single stream multiple media streams and they want to use the single stream
Audio/Video per SSRC segment to report the MOS value, they should Audio/Video per SSRC segment to report the MOS value, they should
be carried in the separate RTP streams with each identified by be carried in the separate RTP streams with each identified by
different SSRC. In this case, multiple QoE Metrics Blocks are different SSRC. In this case, multiple MoS Metrics Blocks are
required to report the MOS value corresponding to each media required to report the MOS value corresponding to each media
stream using single stream Audio/Video per SSRC segment in the stream using single stream Audio/Video per SSRC segment in the
same RTCP XR packet. same RTCP XR packet.
Calg Algorithm ID (CAID) : 8bits Calg Algorithm ID (CAID) : 8bits
The 8-bit CAID is the local identifier of calculation algorithm The 8-bit CAID is the local identifier of calculation algorithm
associated with this segment in the range 1-255 inclusive. associated with this segment in the range 1-255 inclusive.
Payload Type (PT): 7 bits Payload Type (PT): 7 bits
QoE metrics reporting depends on the payload format in use. This MoS Metrics reporting depends on the payload format in use. This
field identifies the format of the RTP payload. For RTP sessions field identifies the format of the RTP payload. For RTP sessions
where multiple payload formats can be negotiated or the payload where multiple payload formats can be negotiated or the payload
format changes during the mid-session), the value of this field format changes during the mid-session), the value of this field
will be used to indicate what payload format was in use for the will be used to indicate what payload format was in use for the
reporting interval. reporting interval.
MOS Value: 16 bits MOS Value: 16 bits
The estimated mean opinion score for multimedia application The estimated mean opinion score for multimedia application
performance is defined as including the effects of delay,loss, performance is defined as including the effects of delay,loss,
skipping to change at page 10, line 26 skipping to change at page 10, line 26
If multiple channels of audio are carried in one RTP stream, each If multiple channels of audio are carried in one RTP stream, each
channel of audio will be viewed as a independent channel(e.g., channel of audio will be viewed as a independent channel(e.g.,
left channel audio, right channel audio). This field is used to left channel audio, right channel audio). This field is used to
identify each channel carried in the same media stream. The identify each channel carried in the same media stream. The
default Channel mapping follows static ordering rule described in default Channel mapping follows static ordering rule described in
the section 4.1 of [RFC3551]. However there are some payload the section 4.1 of [RFC3551]. However there are some payload
formats that use different channel mappings, e.g., AC-3 audio over formats that use different channel mappings, e.g., AC-3 audio over
RTP [RFC4184] only follow AC-3 channel order scheme defined in RTP [RFC4184] only follow AC-3 channel order scheme defined in
[ATSC]. Enhanced AC-3 Audio over RTP [RFC4598] uses dynamic [ATSC]. Enhanced AC-3 Audio over RTP [RFC4598] uses dynamic
channel transform mechanism. In order that the appropriate channel transform mechanism. In order that the appropriate
channel mapping can be determined, QoE reports need to be tied to channel mapping can be determined, MoS metrics reports need to be
an RTP payload format, i.e., including the payload type of the tied to an RTP payload format, i.e., including the payload type of
reported media according to [RFC6792] and using Payload Type to the reported media according to [RFC6792] and using Payload Type
determine the appropriate channel mapping. to determine the appropriate channel mapping.
MOS Value: 13 bits MOS Value: 13 bits
The estimated mean opinion score for multimedia application The estimated mean opinion score for multimedia application
performance is defined as including the effects of delay,loss, performance is defined as including the effects of delay,loss,
discard,jitter and other effects that would affect multimedia discard,jitter and other effects that would affect multimedia
quality . It is expressed in numeric format 6:7 with the value in quality . It is expressed in numeric format 6:7 with the value in
the range 0.0 to 63.992. The valid the measured value ranges from the range 0.0 to 63.992. The valid the measured value ranges from
0.0 to 50.0, corresponding to MoS x 10 as for MoS. If the 0.0 to 50.0, corresponding to MoS x 10 as for MoS. If the
measured value is over ranged, the value 0x1FFE MUST be reported measured value is over ranged, the value 0x1FFE MUST be reported
skipping to change at page 11, line 17 skipping to change at page 11, line 17
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined This section augments the SDP [RFC4566] attribute "rtcp-xr" defined
in [RFC3611] by providing an additional value of "xr-format" to in [RFC3611] by providing an additional value of "xr-format" to
signal the use of the report block defined in this document. Within signal the use of the report block defined in this document. Within
the "xr-format", the syntax element "calgextmap" is an attribute as the "xr-format", the syntax element "calgextmap" is an attribute as
defined in [RFC4566] and used to signal the mapping of the local defined in [RFC4566] and used to signal the mapping of the local
identifier (CAID) in the segment extension defined in section 3.2 to identifier (CAID) in the segment extension defined in section 3.2 to
the calculation algorithm. Specific extensionattributes are defined the calculation algorithm. Specific extensionattributes are defined
by the specification that defines a specific extension name; there by the specification that defines a specific extension name; there
might be several. might be several.
xr-format =/ xr-qoe-block xr-format =/ xr-mos-block
xr-qoe-block = "qoe-metrics" ["=" extmap *("," calgextmap)] xr-mos-block = "mos-metrics" ["=" extmap *("," calgextmap)]
calgextmap = mapentry "=" extensionname [SP extentionattributes] calgextmap = mapentry "=" extensionname [SP extentionattributes]
direction = "sendonly" / "recvonly" / "sendrecv" / "inactive" direction = "sendonly" / "recvonly" / "sendrecv" / "inactive"
mapentry = "calg:" 1*5 DIGIT ["/" direction] mapentry = "calg:" 1*5 DIGIT ["/" direction]
extensionname = "P564";ITU-T P.564 Compliant Algorithm [P.564] extensionname = "P564";ITU-T P.564 Compliant Algorithm [P.564]
/ "G107";ITU-T G.107 [G.107] / "G107";ITU-T G.107 [G.107]
/ "G107_1";ITU-T G.107.1 [G.107.1] / "G107_1";ITU-T G.107.1 [G.107.1]
/ "TS101_329";ETSI TS 101 329-5 Annex E [ ETSI] / "TS101_329";ETSI TS 101 329-5 Annex E [ ETSI]
/"JJ201_1 ";TTC JJ201.1 [TTC] /"JJ201_1 ";TTC JJ201.1 [TTC]
/"P1201_1";ITU-T P.1201.2 [P.1201.1] /"P1201_1";ITU-T P.1201.2 [P.1201.1]
/"P1201_2";ITU-T P.1201.2 [P.1201.2] /"P1201_2";ITU-T P.1201.2 [P.1201.2]
skipping to change at page 12, line 10 skipping to change at page 12, line 10
segment defined in the section 3.2 is mapped to a string using an segment defined in the section 3.2 is mapped to a string using an
attribute of the form: attribute of the form:
a=calgextmap:<value> ["/"<direction>] <name> [<extensionattributes>] a=calgextmap:<value> ["/"<direction>] <name> [<extensionattributes>]
where <name> is a calculation algorithm name, as above, <value> is where <name> is a calculation algorithm name, as above, <value> is
the local identifier (CAID)of the calculation algorithm associated the local identifier (CAID)of the calculation algorithm associated
with the segment defined in this document and is an integer in the with the segment defined in this document and is an integer in the
valid range inclusive. valid range inclusive.
Example: Example:
a=rtcp-xr:qoe-metrics=calg:1=G107,calg:2=P1202_1 a=rtcp-xr:mos-metrics=calg:1=G107,calg:2=P1202_1
A usable mapping MUST use IDs in the valid range, and each ID in this A usable mapping MUST use IDs in the valid range, and each ID in this
range MUST be unique and used only once for each stream or each range MUST be unique and used only once for each stream or each
channel in the stream. channel in the stream.
The mapping MUST be provided per media stream (in the media-level The mapping MUST be provided per media stream (in the media-level
section(s) of SDP, i.e., after an "m=" line). section(s) of SDP, i.e., after an "m=" line).
The syntax element "mosref" is referred to the media resolution The syntax element "mosref" is referred to the media resolution
relative reference (e.g., Narrowband (3.4kHz) Speech and Standard relative reference (e.g., Narrowband (3.4kHz) Speech and Standard
Definition (SD) Resolution Video with lower resolution, Wideband Definition (SD) Resolution Video with lower resolution, Wideband
(7kHz) Speech and High Definition (HD) Resolution Video with higher (7kHz) Speech and High Definition (HD) Resolution Video with higher
resolution). MOS scores reported in the QoE block might vary with resolution). MOS scores reported in the mos metrics block might vary
the MoS reference; For example, MOS values for narrowband, wideband with the MoS reference; For example, MOS values for narrowband,
codecs occupy the same range but SHOULD be reported in different wideband codecs occupy the same range but SHOULD be reported in
value. For video application, MoS scores for SD resolution, HD different value. For video application, MoS scores for SD
resolution video also occupy the same ranges and SHOULD be reported resolution, HD resolution video also occupy the same ranges and
in different value. SHOULD be reported in different value.
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] applies. In the offer answer context, the defined in [RFC3611] applies. In the offer answer context, the
signaling described above might be used in three ways: signaling described above might be used in three ways:
o asymmetric behavior (segment extensions sent in only one o asymmetric behavior (segment extensions sent in only one
direction), direction),
o the offer of mutually exclusive alternatives, or o the offer of mutually exclusive alternatives, or
skipping to change at page 14, line 12 skipping to change at page 14, line 12
Note that the range 4096-4351 for these negotiation identifiers is Note that the range 4096-4351 for these negotiation identifiers is
deliberately restricted to allow expansion of the range of valid deliberately restricted to allow expansion of the range of valid
identifiers in future. Segment extensions with an identifier outside identifiers in future. Segment extensions with an identifier outside
the valid range cannot, of course, be used. the valid range cannot, of course, be used.
Example (port numbers, RTP profiles, payload IDs and rtpmaps, etc. Example (port numbers, RTP profiles, payload IDs and rtpmaps, etc.
all omitted for brevity): all omitted for brevity):
The offer: The offer:
a=rtcp-xr:qoe- metrics=calg:4906=P1201_l,calg:4906=P1202_l,calg: a=rtcp-xr:mos-
4907=G107 metrics=calg:4906=P1201_l,calg:4906=P1202_l,calg:4907=G107
The answerer is interested in transmission P.1202.1 on lower The answerer is interested in transmission P.1202.1 on lower
resolution application, but doesn't support P.1201.1 on lower resolution application, but doesn't support P.1201.1 on lower
resolution application at all. It is interested in transmission resolution application at all. It is interested in transmission
G.107. It therefore adjusts the declarations: G.107. It therefore adjusts the declarations:
a=rtcp-xr:qoe-metrics=calg:1=P1202_l,calg:2=G107 a=rtcp-xr:mos-metrics=calg:1=P1202_l,calg:2=G107
5. IANA Considerations 5. IANA Considerations
New block types for RTCP XR are subject to IANA registration. For New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to general guidelines on IANA considerations for RTCP XR, refer to
[RFC3611]. [RFC3611].
5.1. New RTCP XR Block Type value 5.1. New RTCP XR Block Type value
This document assigns the block type value QMB in the IANA " RTP This document assigns the block type value MMB in the IANA " RTP
Control Protocol Extended Reports (RTCP XR) Block Type Registry" to Control Protocol Extended Reports (RTCP XR) Block Type Registry" to
the "QoE Metrics Block". the "MoS Metrics Block".
[Note to RFC Editor: please replace QMB with the IANA provided RTCP [Note to RFC Editor: please replace MMB with the IANA provided RTCP
XR block type for this block.] XR block type for this block.]
5.2. New RTCP XR SDP Parameter 5.2. New RTCP XR SDP Parameter
This document also registers a new parameter "qoe-metrics" in the " This document also registers a new parameter "mos-metrics" in the "
RTP Control Protocol Extended Reports (RTCP XR) Session Description RTP Control Protocol Extended Reports (RTCP XR) Session Description
Protocol (SDP) Parameters Registry". Protocol (SDP) Parameters Registry".
5.3. The SDP calgextmap Attribute 5.3. The SDP calgextmap Attribute
This section contains the information required by [RFC4566] for an This section contains the information required by [RFC4566] for an
SDP attribute. SDP attribute.
o contact name, email address: o contact name, email address:
Qin Wu Qin Wu
skipping to change at page 15, line 21 skipping to change at page 15, line 21
o a one-paragraph explanation of the purpose of the attribute: This o a one-paragraph explanation of the purpose of the attribute: This
attribute defines the mapping from the local identifier (CAID) in attribute defines the mapping from the local identifier (CAID) in
the segment extension defined in section 3.2 into the calculation the segment extension defined in section 3.2 into the calculation
algorithm name as documented in specifications and appropriately algorithm name as documented in specifications and appropriately
registered. registered.
o a specification of appropriate attribute values for this o a specification of appropriate attribute values for this
attribute: see RFC xxxx. attribute: see RFC xxxx.
5.4. New registry of calculation algorithms 5.4. New registry of calculation algorithms
This document creates a new registry to be called "RTCP XR QoE metric This document creates a new registry to be called "RTCP XR MoS Metric
block - multimedia application Calculation Algorithm" as a sub- block - multimedia application Calculation Algorithm" as a sub-
registry of the "RTP Control Protocol Extended Reports (RTCP XR) registry of the "RTP Control Protocol Extended Reports (RTCP XR)
Block Type Registry". This registry applies to the multimedia Block Type Registry". This registry applies to the multimedia
session where each type of media are sent in a separate RTP stream session where each type of media are sent in a separate RTP stream
and also applies to the session where Multi-channel audios are and also applies to the session where Multi-channel audios are
carried in one RTP stream. Policies for this new registry are as carried in one RTP stream. Policies for this new registry are as
follows: follows:
o The information required to support this assignment is an o The information required to support this assignment is an
unambiguous definition of the new metric, covering the base unambiguous definition of the new metric, covering the base
skipping to change at page 16, line 32 skipping to change at page 16, line 32
P1202_1 ITU-T P.1202.1 [P.1202.1] Video P1202_1 ITU-T P.1202.1 [P.1202.1] Video
P1202_2 ITU-T P.1202.2 [P.1202.2] Video P1202_2 ITU-T P.1202.2 [P.1202.2] Video
6. Security Considerations 6. Security Considerations
The new RTCP XR report blocks proposed in this document introduces no The new RTCP XR report blocks proposed in this document introduces no
new security considerations beyond those described in [RFC3611]. new security considerations beyond those described in [RFC3611].
7. Authors 7. Authors
This draft merges ideas from two drafts addressing the QoE metric This draft merges ideas from two drafts addressing the MoS Metric
Reporting issue. The authors of these drafts are listed below (in Reporting issue. The authors of these drafts are listed below (in
alphabetical order): alphabetical order):
Alan Clark < alan.d.clark@telchemy.com > Alan Clark < alan.d.clark@telchemy.com >
Geoff Hunt < r.geoff.hunt@gmail.com > Geoff Hunt < r.geoff.hunt@gmail.com >
Martin Kastner < martin.kastner@telchemy.com > Martin Kastner < martin.kastner@telchemy.com >
Kai Lee < leekai@ctbri.com.cn > Kai Lee < leekai@ctbri.com.cn >
Roland Schott < roland.schott@telekom.de > Roland Schott < roland.schott@telekom.de >
Qin Wu < sunseawq@huawei.com > Qin Wu < sunseawq@huawei.com >
Glen Zorn < gwz@net-zen.net > Glen Zorn < gwz@net-zen.net >
skipping to change at page 22, line 46 skipping to change at page 22, line 46
* Measurement Timing: See section 3, 3rd paragraph [RFCXXXX] for * Measurement Timing: See section 3, 3rd paragraph [RFCXXXX] for
measurement timing and section 3.1 [RFCXXXX] for Interval measurement timing and section 3.1 [RFCXXXX] for Interval
Metric flag. Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and applications: See section 1.4 [RFCXXXX].
* Reporting model: See RFC3611. * Reporting model: See RFC3611.
Appendix C. Change Log Appendix C. Change Log
C.1. draft-ietf-xrblock-rtcp-xr-qoe-09 C.1. draft-ietf-xrblock-rtcp-xr-qoe-10
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Replace QoE metrics with MoS metrics.
C.2. draft-ietf-xrblock-rtcp-xr-qoe-09
The following are the major changes compared to previous version:
o Address comments recieved from WGLC, PM-DIR Review and SDP review. o Address comments recieved from WGLC, PM-DIR Review and SDP review.
o Change an existing SDP attribute 'extmap' to new SDP attribute o Change an existing SDP attribute 'extmap' to new SDP attribute
'calgextmap' and add new SDP attribute registry. 'calgextmap' and add new SDP attribute registry.
o Add Reference to G.107.1, P.862.1, P.862.2 and P.863 for new o Add Reference to G.107.1, P.862.1, P.862.2 and P.863 for new
calculation algorithms. calculation algorithms.
o Add MoS type attribute to distinguish different MoS type. o Add MoS type attribute to distinguish different MoS type.
o Other Editorial changes. o Other Editorial changes.
C.2. draft-ietf-xrblock-rtcp-xr-qoe-08 C.3. draft-ietf-xrblock-rtcp-xr-qoe-08
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Remove mostype attribute from SDP extension since it can inferred o Remove mostype attribute from SDP extension since it can inferred
from payload type. from payload type.
o Clarify mosref attribute usage in the O/A. o Clarify mosref attribute usage in the O/A.
C.3. draft-ietf-xrblock-rtcp-xr-qoe-07 C.4. draft-ietf-xrblock-rtcp-xr-qoe-07
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Some editorial changes to get in line with burst gap related o Some editorial changes to get in line with burst gap related
draft. draft.
o Add an appendix to apply RFC6390 template. o Add an appendix to apply RFC6390 template.
C.4. draft-ietf-xrblock-rtcp-xr-qoe-06 C.5. draft-ietf-xrblock-rtcp-xr-qoe-06
The following are the major changes compared to previous two The following are the major changes compared to previous two
versions: versions:
o A few Contact information update. o A few Contact information update.
o A few Acknowledgement section update. o A few Acknowledgement section update.
C.5. draft-ietf-xrblock-rtcp-xr-qoe-04 C.6. draft-ietf-xrblock-rtcp-xr-qoe-04
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Split two references P.NAMS and P.NBAMS into four references. o Split two references P.NAMS and P.NBAMS into four references.
o SDP signaling update. o SDP signaling update.
o Add one example to explain User QoE evaluation for video stream o Add one example to explain User QoE evaluation for video stream
C.6. draft-ietf-xrblock-rtcp-xr-qoe-03 C.7. draft-ietf-xrblock-rtcp-xr-qoe-03
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Add one new reference to support TTC JJ201.01. o Add one new reference to support TTC JJ201.01.
o Update two references P.NAMS and P.NBAMS. o Update two references P.NAMS and P.NBAMS.
o Other Editorial changes based on comments applied to PDV and Delay o Other Editorial changes based on comments applied to PDV and Delay
drafts. drafts.
C.7. draft-ietf-xrblock-rtcp-xr-qoe-02 C.8. draft-ietf-xrblock-rtcp-xr-qoe-02
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Remove leftmost second bit since it is ueeless. o Remove leftmost second bit since it is ueeless.
o Change 13bits MoS value field into 14 bits to increase MoS o Change 13bits MoS value field into 14 bits to increase MoS
precision. precision.
o Fix some typo and make some editorial changes. o Fix some typo and make some editorial changes.
C.8. draft-ietf-xrblock-rtcp-xr-qoe-01 C.9. draft-ietf-xrblock-rtcp-xr-qoe-01
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Remove layered support from the QoE metric draft. o Remove layered support from the QoE Metric draft.
o Allocate 7 bits in the block header for payload type to indicate o Allocate 7 bits in the block header for payload type to indicate
what type of payload format is in use and add associated what type of payload format is in use and add associated
definition of payload type. definition of payload type.
o Clarify using Payload Type to determine the appropriate channel o Clarify using Payload Type to determine the appropriate channel
mapping in the definition of Channel Identifier. mapping in the definition of Channel Identifier.
C.9. draft-ietf-xrblock-rtcp-xr-qoe-00 C.10. draft-ietf-xrblock-rtcp-xr-qoe-00
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Allocate one more bit in the single stream per SSC segment to get o Allocate one more bit in the single stream per SSC segment to get
alignment with the other two segment type. alignment with the other two segment type.
Authors' Addresses Authors' Addresses
Alan Clark Alan Clark
Telchemy Incorporated Telchemy Incorporated
2905 Premiere Parkway, Suite 280 2905 Premiere Parkway, Suite 280
 End of changes. 51 change blocks. 
78 lines changed or deleted 85 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/