draft-ietf-xrblock-rtcp-xr-qoe-12.txt   draft-ietf-xrblock-rtcp-xr-qoe-13.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: March 30, 2014 Huawei Expires: July 11, 2014 Huawei
R. Schott R. Schott
Deutsche Telekom Deutsche Telekom
G. Zorn G. Zorn
Network Zen Network Zen
September 24, 2013 January 9, 2014
RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MOS Metric RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MOS Metric
Reporting Reporting
draft-ietf-xrblock-rtcp-xr-qoe-12 draft-ietf-xrblock-rtcp-xr-qoe-13
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 MOS 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
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 March 30, 2014. This Internet-Draft will expire on July 11, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 4, line 37 skipping to change at page 4, line 37
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 MOS 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 (Quality of Experience) 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 consists of content and codec related factors in the second category consists of content and codec related
factors such as codec type and loss recovery technique, coding bit factors such as codec type and loss recovery technique, coding bit
rate, packetization scheme, and content characteristics rate, packetization scheme, and content characteristics
Transport-specific factors may be insufficient to infer real time Transport-specific factors may be insufficient to infer real time
skipping to change at page 8, line 47 skipping to change at page 8, line 47
multiple media streams and they want to use the single channel multiple media streams and they want to use the single channel
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 MOS 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 channel Audio/Video per SSRC segment in the stream using single channel Audio/Video per SSRC segment in the
same RTCP XR packet. same RTCP XR packet.
Calculation Algorithm ID (CAID) : 8 bits Calculation Algorithm ID (CAID) : 8 bits
The 8-bit CAID is the local identifier of calculation algorithm The 8-bit CAID is the session specific reference to the
associated with this segment in the range 1-255 inclusive. calculation algorithm and associated qualifiers indicated in SDP
(see Section 4.1) and used to compute QoE scores for this segment
Payload Type (PT): 7 bits Payload Type (PT): 7 bits
MOS Metrics reporting depends on the payload format in use. This MOS Metrics reporting depends on the payload format in use. This
field identifies the RTP payload type in use during the reporting field identifies the RTP payload type in use during the reporting
interval. The binding between RTP payload types and RTP payload interval. The binding between RTP payload types and RTP payload
formats is configured via a signalling protocol, for example an formats is configured via a signalling protocol, for example an
SDP offer/answer exchange. If the RTP payload type used is SDP offer/answer exchange. If the RTP payload type used is
changed during an RTP session, separate reports SHOULD be sent for changed during an RTP session, separate reports SHOULD be sent for
each RTP payload type, with corresponding measurement information each RTP payload type, with corresponding measurement information
blocks indicating the time period to which they relate. blocks indicating the time period to which they relate.
Note that the use of this Report Block with MPEG Transport streams Note that the use of this Report Block with MPEG Transport streams
carried over RTP is undefined as each MPEG Transport stream may carried over RTP is undefined as each MPEG Transport stream may
use distinct audio or vide codecs and the indication of the use distinct audio or video codecs and the indication of the
encoding of these is within the MPEG Transport stream and does not encoding of these is within the MPEG Transport stream and does not
use RTP payloads. use RTP payloads.
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,
discard, jitter and other effects that would affect media quality. discard, jitter and other effects that would affect media quality.
A 1-5 MOS score is multiplied by 10 and then represented in the A 1-5 MOS score is multiplied by 10 and then represented in the
8:8 format. If the measured value is over range, the value 8:8 format. If the measured value is over range, the value
skipping to change at page 9, line 48 skipping to change at page 9, line 48
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Segment Type (S): 1 bit Segment Type (S): 1 bit
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 one identifies this as a multi-channel audio report block. A one identifies this as a multi-channel audio
segment. segment.
Calculation Algorithm ID (CAID) : 8 bits Calculation Algorithm ID (CAID) : 8 bits
The 8-bit ID is the local identifier of this segment in the range The 8-bit CAID is the session specific reference to the
1-255 inclusive. calculation algorithm and associated qualifiers indicated in SDP
(see Section 4.1) and used to compute QoE scores for this segment
Payload Type (PT): 7 bits Payload Type (PT): 7 bits
As defined in Section 3.2.1 of this document. As defined in Section 3.2.1 of this document.
Channel Identifier (CHID): 3 bits Channel Identifier (CHID): 3 bits
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
skipping to change at page 11, line 9 skipping to change at page 11, line 9
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-mos-block xr-format =/ xr-mos-block
xr-mos-block = "mos-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*3 DIGIT ["/" direction]
;Values other than 4095~4351 are valid ; Values in the range 1-255 are valid
; if needed, 0 can be used to indicate that
; an algorithm is rejected
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]
/"P1202_1";ITU-T P.1202.1 [P.1202.1] /"P1202_1";ITU-T P.1202.1 [P.1202.1]
/"P1202_2";ITU-T P.1202.2 [P.1202.2] /"P1202_2";ITU-T P.1202.2 [P.1202.2]
/"P.862.2";ITU-T P.862.2 [P.862.2] /"P.862.2";ITU-T P.862.2 [P.862.2]
/"P.863"; ITU-T P.863 [P.863] /"P.863"; ITU-T P.863 [P.863]
/ non-ws-string / non-ws-string
extensionattributes = mosref extensionattributes = mosref
/attributes-ext /attributes-ext
mosref = "mosref=" ("l"; lower resolution mosref = "mosref=" ("l"; lower resolution
/"m"; middle resolution /"m"; middle resolution
/ "h";higher resolution / "h";higher resolution
/ non-ws-string) / non-ws-string)
mostype = "mostype=" ("e"; Estimated MOS [P.800.1]
/"s";subjective MOS [P.800.1]
/"o";objective MOS [P.800.1]
/non-ws-string)
attributes-ext = non-ws-string attributes-ext = non-ws-string
SP = <Define in RFC5234> SP = <Define in RFC5234>
non-ws-string = 1*(%x21-FF) non-ws-string = 1*(%x21-FF)
Each local identifier (CAID)of calculation algorithm used in the Each local identifier (CAID)of calculation algorithm used in the
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>]
skipping to change at page 21, line 34 skipping to change at page 21, line 34
* 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 B. Change Log Appendix B. Change Log
B.1. draft-ietf-xrblock-rtcp-xr-qoe-10 B.1. draft-ietf-xrblock-rtcp-xr-qoe-13
o Incorporated comments from Gen Art review
o Amended SDP description in 4.1
o Overall clean up
B.2. 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. o Replace QoE metrics with MOS metrics.
B.2. draft-ietf-xrblock-rtcp-xr-qoe-09 B.3. draft-ietf-xrblock-rtcp-xr-qoe-09
The following are the major changes compared to previous version: 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.
B.3. draft-ietf-xrblock-rtcp-xr-qoe-08 B.4. 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.
B.4. draft-ietf-xrblock-rtcp-xr-qoe-07 B.5. 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.
B.5. draft-ietf-xrblock-rtcp-xr-qoe-06 B.6. 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.
B.6. draft-ietf-xrblock-rtcp-xr-qoe-04 B.7. 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
B.7. draft-ietf-xrblock-rtcp-xr-qoe-03 B.8. 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.
B.8. draft-ietf-xrblock-rtcp-xr-qoe-02 B.9. 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.
B.9. draft-ietf-xrblock-rtcp-xr-qoe-01 B.10. 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.
B.10. draft-ietf-xrblock-rtcp-xr-qoe-00 B.11. 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 channel per SSC segment to get o Allocate one more bit in the single channel 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. 23 change blocks. 
29 lines changed or deleted 34 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/