draft-ietf-xrblock-rtcp-xr-qoe-14.txt   draft-ietf-xrblock-rtcp-xr-qoe-15.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Intended status: Standards Track Q. Wu Intended status: Standards Track Q. Wu
Expires: August 17, 2014 Huawei Expires: August 17, 2014 Huawei
R. Schott R. Schott
Deutsche Telekom Deutsche Telekom
G. Zorn G. Zorn
Network Zen Network Zen
February 13, 2014 February 13, 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-14 draft-ietf-xrblock-rtcp-xr-qoe-15
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 mean opinion score (MOS) parameters that allow the reporting of mean opinion score (MOS)
Metrics for use in a range of RTP applications. Metrics for use in a range of RTP applications.
Status of this Memo Status of this Memo
skipping to change at page 2, line 40 skipping to change at page 3, line 35
5.3. The SDP calgextmap Attribute . . . . . . . . . . . . . . . 15 5.3. The SDP calgextmap Attribute . . . . . . . . . . . . . . . 15
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 . . . . . . . . . . . . . . . . . . . . . . . 17 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.1. Normative References . . . . . . . . . . . . . . . . . . . 17 9.1. Normative References . . . . . . . . . . . . . . . . . . . 17
9.2. Informative References . . . . . . . . . . . . . . . . . . 18 9.2. Informative References . . . . . . . . . . . . . . . . . . 18
Appendix A. Metrics represented using RFC6390 Template . . . . . 19 Appendix A. Metrics represented using RFC6390 Template . . . . . 19
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 22 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 22
B.1. draft-ietf-xrblock-rtcp-xr-qoe-14 . . . . . . . . . . . . 22 B.1. draft-ietf-xrblock-rtcp-xr-qoe-15 . . . . . . . . . . . . 22
B.2. draft-ietf-xrblock-rtcp-xr-qoe-10 . . . . . . . . . . . . 22 B.2. draft-ietf-xrblock-rtcp-xr-qoe-14 . . . . . . . . . . . . 22
B.3. draft-ietf-xrblock-rtcp-xr-qoe-09 . . . . . . . . . . . . 22 B.3. draft-ietf-xrblock-rtcp-xr-qoe-10 . . . . . . . . . . . . 22
B.4. draft-ietf-xrblock-rtcp-xr-qoe-08 . . . . . . . . . . . . 23 B.4. draft-ietf-xrblock-rtcp-xr-qoe-09 . . . . . . . . . . . . 23
B.5. draft-ietf-xrblock-rtcp-xr-qoe-07 . . . . . . . . . . . . 23 B.5. draft-ietf-xrblock-rtcp-xr-qoe-08 . . . . . . . . . . . . 23
B.6. draft-ietf-xrblock-rtcp-xr-qoe-06 . . . . . . . . . . . . 23 B.6. draft-ietf-xrblock-rtcp-xr-qoe-07 . . . . . . . . . . . . 23
B.7. draft-ietf-xrblock-rtcp-xr-qoe-04 . . . . . . . . . . . . 23 B.7. draft-ietf-xrblock-rtcp-xr-qoe-06 . . . . . . . . . . . . 23
B.8. draft-ietf-xrblock-rtcp-xr-qoe-03 . . . . . . . . . . . . 23 B.8. draft-ietf-xrblock-rtcp-xr-qoe-04 . . . . . . . . . . . . 23
B.9. draft-ietf-xrblock-rtcp-xr-qoe-02 . . . . . . . . . . . . 23 B.9. draft-ietf-xrblock-rtcp-xr-qoe-03 . . . . . . . . . . . . 23
B.10. draft-ietf-xrblock-rtcp-xr-qoe-01 . . . . . . . . . . . . 24 B.10. draft-ietf-xrblock-rtcp-xr-qoe-02 . . . . . . . . . . . . 24
B.11. draft-ietf-xrblock-rtcp-xr-qoe-00 . . . . . . . . . . . . 24 B.11. draft-ietf-xrblock-rtcp-xr-qoe-01 . . . . . . . . . . . . 24
B.12. draft-ietf-xrblock-rtcp-xr-qoe-00 . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
1.1. MOS 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
skipping to change at page 12, line 48 skipping to change at page 12, line 48
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
o the offer of more segments than can be sent in a single session. o the offer of more segments than can be sent in a single session.
A direction attribute MAY be included in a calgextmap; without it, A direction attribute MAY be included in a calgextmap; without it,
the direction implicitly inherits, of course, from the RTCP stream the direction implicitly inherits, of course, from the RTCP stream
direction. direction.
Segment extensions, with their directions, MAY be signaled for an Segment extensions, with their directions, MAY be signaled for an
"inactive" stream. An extension direction SHOULD be compatible with "inactive" stream. An extension direction MUST be compatible with
the stream direction. If a segment extension in the SDP offer is the stream direction. If a segment extension in the SDP offer is
marked as "sendonly" and the answerer desires to receive it, the marked as "sendonly" and the answerer desires to receive it, the
extension MUST be marked as "recvonly" in the SDP answer. An extension MUST be marked as "recvonly" in the SDP answer. An
answerer that has no desire to receive the extension or does not answerer that has no desire to receive the extension or does not
understand the extension SHOULD remove it from the SDP answer. understand the extension SHOULD NOT include it from the SDP answer.
If a segment extension is marked as "recvonly" in the SDP offer and If a segment extension is marked as "recvonly" in the SDP offer and
the answerer desires to send it, the extension MUST be marked as the answerer desires to send it, the extension MUST be marked as
"sendonly" in the SDP answer. An answerer that has no desire to, or "sendonly" in the SDP answer. An answerer that has no desire to, or
is unable to, send the extension SHOULD remove it from the SDP is unable to, send the extension SHOULD NOT include it from the SDP
answer. answer.
If a segment extension is offered as "sendrecv", explicitly or If a segment extension is offered as "sendrecv", explicitly or
implicitly, and asymmetric behavior is desired, the SDP MAY be implicitly, and asymmetric behavior is desired, the SDP MAY be
modified to modify or add direction qualifiers for that segment modified to modify or add direction qualifiers for that segment
extension. extension.
A mosref attribute and mos type attribute MAY be included in an A mosref attribute and mos type attribute MAY be included in an
calgextmap; without it, the mosref and most type attribute implicitly calgextmap; without it, the mosref and most type attribute implicitly
inherits, of course, from the name attribute (e.g., P.1201.1 inherits, of course, from the name attribute (e.g., P.1201.1
skipping to change at page 15, line 10 skipping to change at page 15, line 10
5.2. New RTCP XR SDP Parameter 5.2. New RTCP XR SDP Parameter
This document also registers a new parameter "mos-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: ietf
Qin Wu
sunseawq@huawei.com
o attribute name (as it will appear in SDP): calgextmap o attribute name (as it will appear in SDP): calgextmap
o long-form attribute name in English: calculation algorithm map o long-form attribute name in English: calculation algorithm map
definition definition
o type of attribute (session level, media level, or both): both o type of attribute (session level, media level, or both): both
o whether the attribute value is subject to the charset attribute: o whether the attribute value is subject to the charset attribute:
not subject to the charset attribute not subject to the charset attribute
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
skipping to change at page 22, line 36 skipping to change at page 22, 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-14 B.1. draft-ietf-xrblock-rtcp-xr-qoe-15
The following are the major changes compared to previous version:
o Some Editorial Changes.
B.2. draft-ietf-xrblock-rtcp-xr-qoe-14
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Add some texts to address IESG review comments. o Add some texts to address IESG review comments.
B.2. draft-ietf-xrblock-rtcp-xr-qoe-10 B.3. 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.3. draft-ietf-xrblock-rtcp-xr-qoe-09 B.4. 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.4. draft-ietf-xrblock-rtcp-xr-qoe-08 B.5. 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.5. draft-ietf-xrblock-rtcp-xr-qoe-07 B.6. 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.6. draft-ietf-xrblock-rtcp-xr-qoe-06 B.7. 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.7. draft-ietf-xrblock-rtcp-xr-qoe-04 B.8. 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.8. draft-ietf-xrblock-rtcp-xr-qoe-03 B.9. 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.9. draft-ietf-xrblock-rtcp-xr-qoe-02 B.10. 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.10. draft-ietf-xrblock-rtcp-xr-qoe-01 B.11. 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.11. draft-ietf-xrblock-rtcp-xr-qoe-00 B.12. 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. 19 change blocks. 
34 lines changed or deleted 33 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/