draft-ietf-xrblock-rtcp-xr-qoe-00.txt   draft-ietf-xrblock-rtcp-xr-qoe-01.txt 
Network Working Group G. Hunt Network Working Group G. Hunt
Internet-Draft Unaffiliated Internet-Draft Unaffiliated
Intended status: Standards Track A. Clark Intended status: Standards Track A. Clark
Expires: August 5, 2012 Telchemy Expires: November 15, 2012 Telchemy
Q. Wu Q. Wu
Huawei Huawei
R. Schott R. Schott
DT DT
G. Zorn G. Zorn
Network Zen Network Zen
February 2, 2012 May 14, 2012
RTCP XR Blocks for QoE Metric Reporting RTCP XR Blocks for QoE Metric Reporting
draft-ietf-xrblock-rtcp-xr-qoe-00 draft-ietf-xrblock-rtcp-xr-qoe-01
Abstract Abstract
This document defines an RTCP XR Report Block and associated SDP This document defines an RTCP XR Report Block including two new
parameters that allow the reporting of QoE metrics for use in a range segment types and associated SDP parameters that allow the reporting
of RTP applications. of QoE metrics for use in a range 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 August 5, 2012. This Internet-Draft will expire on November 15, 2012.
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
skipping to change at page 2, line 23 skipping to change at page 2, line 23
1.1. QoE Metrics Report Block . . . . . . . . . . . . . . . . . 3 1.1. QoE Metrics Report Block . . . . . . . . . . . . . . . . . 3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
3. QoE Metrics Block . . . . . . . . . . . . . . . . . . . . . . 5 3. QoE Metrics Block . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Metric Block Structure . . . . . . . . . . . . . . . . . . 5 3.1. Metric Block Structure . . . . . . . . . . . . . . . . . . 5
3.2. Definition of Fields in QoE Metrics Block . . . . . . . . 6 3.2. Definition of Fields in QoE Metrics Block . . . . . . . . 6
3.2.1. Single Stream per SSRC Segment . . . . . . . . . . . . 7 3.2.1. Single Stream per SSRC Segment . . . . . . . . . . . . 7
3.2.2. Multi-Layer per SSRC Segment . . . . . . . . . . . . . 9 3.2.2. Multi-Channel per SSRC Segment . . . . . . . . . . . . 9
3.2.3. Multi-Channel per SSRC Segment . . . . . . . . . . . . 10 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 10
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 11
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 12 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 11
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12 5.3. Contact information for registrations . . . . . . . . . . 11
5.3. Contact information for registrations . . . . . . . . . . 12
5.4. New registry of calculation algorithms for single 5.4. New registry of calculation algorithms for single
stream per SSRC segment . . . . . . . . . . . . . . . . . 12 stream per SSRC segment . . . . . . . . . . . . . . . . . 11
5.5. New registry of calculation algorithms for multi-layer 5.5. New registry of calculation algorithms for
per SSRC segment . . . . . . . . . . . . . . . . . . . . . 13 multi-channel per SSRC segment . . . . . . . . . . . . . . 12
5.6. New registry of calculation algorithms for 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
multi-channel per SSRC segment . . . . . . . . . . . . . . 14 7. Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
7. Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 9.2. Informative References . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . . 15 A.1. draft-ietf-xrblock-rtcp-xr-qoe-01 . . . . . . . . . . . . 15
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 16 A.2. draft-ietf-xrblock-rtcp-xr-qoe-00 . . . . . . . . . . . . 15
A.1. draft-ietf-xrblock-rtcp-xr-qoe-00 . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
1.1. QoE Metrics Report Block 1.1. QoE Metrics Report Block
This draft defines a new block type to augment those defined in This draft 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 multimedia quality using The new block type provides information on multimedia quality using
one of several standard metrics. one of several standard metrics.
skipping to change at page 6, line 29 skipping to change at page 6, line 29
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.2. Definition of Fields in QoE Metrics Block 3.2. Definition of Fields in QoE Metrics Block
Block type (BT): 8 bits Block type (BT): 8 bits
The QoE Metrics Block is identified by the constant <SMQ>. The QoE Metrics Block is identified by the constant <SMQ>.
Interval Metric flag (I): 2 bit Interval Metric flag (I): 2 bit
This field is used to indicate whether the Basic Loss/Discard This field is used to indicate whether the QoE metrics are
metrics are Interval or Cumulative metrics, that is, whether the Interval or Cumulative metrics, that is, whether the reported
reported values applies to the most recent measurement interval values applies to the most recent measurement interval duration
duration between successive metrics reports (I=01) (the Interval between successive metrics reports (I=10) (the Interval Duration)
Duration) or to the accumulation period characteristic of or to the accumulation period characteristic of cumulative
cumulative measurements (I=00) (the Cumulative Duration) or to the measurements (I=11) (the Cumulative Duration) or is a sampled
value of a continuously measured or calculated that has been instantaneous value (I=01) (Sampled Value).
sampled at end of the interval (I=10) (Sampled Value).
Rsd.:6 bits Rsd.: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
MUST be ignored by the receiver. MUST be ignored by the receiver.
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 QoE 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 three segment types : single stream per SSRC segment, There are two segment types defined in this document: single
multi-channel audio per SSRC segment, multi-layer per SSRC stream per SSRC segment, multi-channel audio per SSRC segment.
segment. Multi-channel per SSRC segment and multi-layer per SSRC Multi-channel per SSRC segment is used to deal with the case where
segment are used to deal with the case where multiple elementary multiple elementary streams or components are carried in one RTP
streams or components are carried in one RTP stream while single stream while single stream per SSRC segment is used to deal with
stream per SSRC segment is used to deal with the case where there the case where there is no more than one elementary stream or
is no more than one elementary stream or component in one RTP component in one RTP stream. The left two bits of the section
stream. The left two bits of the section determine its type. If determine its type. If the leftmost bit of the segment is zero,
the leftmost bit of the segment is zero, then it is single stream then it is single stream segment. If the leftmost bit is one and
segment. If the leftmost bit is one and the second bit is zero, the second bit is zero, then it is multi-channel audio segment.
then it is multi-channel audio segment, if the leftmost bit is one Note that two segment types can not be present in the same metric
and the second bit is one, then it is multi- view segment. Note block.
that in these three segment type,any two segment types can not be
present in the same metric block.
3.2.1. Single Stream per SSRC Segment 3.2.1. Single Stream per SSRC Segment
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|R| MT |CAlg | Rsv. | MOS Value | |0|R| MT |CAlg | PT |Rsv. | MOS Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Segment Type ( S): 1 bit Segment Type ( S): 1 bit
A zero identifies this as a single stream segment. Single stream A zero identifies this as a single stream segment. Single stream
means there is only one elementary stream carried in one RTP means there is only one elementary stream carried in one RTP
stream. The single stream segment can be used to report the MoS stream. The single stream segment can be used to report the MoS
value associated with this elementary stream. If there are value associated with this elementary stream. If there are
multiple streams and they want to use the single stream segment to multiple streams and they want to use the single stream segment to
report the MOS value, they should be carried in the separate RTP report the MOS value, they should be carried in the separate RTP
skipping to change at page 9, line 6 skipping to change at page 8, line 46
Calculation Algorithm (CALg):3 bits Calculation Algorithm (CALg):3 bits
000 - ITU-T P.564 Compliant Algorithm [P.564] (Voice) 000 - ITU-T P.564 Compliant Algorithm [P.564] (Voice)
001 - G.107 [G.107] (Voice) 001 - G.107 [G.107] (Voice)
010 - ETSI TS 101 329-5 Annex E [ ETSI] (Voice) 010 - ETSI TS 101 329-5 Annex E [ ETSI] (Voice)
011 - ITU-T P.NAMS [P.NAMS] (Multimedia) 011 - ITU-T P.NAMS [P.NAMS] (Multimedia)
100 - ITU-T P.NBAMS [P.NBAMS] (Multimedia) 100 - ITU-T P.NBAMS [P.NBAMS] (Multimedia)
101~111 - Reserved for future extension. 101~111 - Reserved for future extension.
Rsd.:7 bits Payload Type (PT): 7 bits
QoE meric reporting for a single stream will depend on the payload
format in use. This field identifies the format of the RTP
payload. For RTP sessions where multiple payload formats can be
negotiated or the payload format changes during the mid-session),
the value of this field will be used to indicate what payload
format was in use for the reporting interval.
Rsd.:3 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
MUST be ignored by the receiver. MUST be ignored by the receiver.
MOS Value: 16 bits MOS Value: 13 bits
The estimated mean opinion score for multimedia application The estimated mean opinion score for multimedia application
quality is defined as including the effects of delay,loss, quality 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 8:8 with the value in quality . It is expressed in numeric format 6:7 with the value in
the range 0.0 to 255.996. The valid the measured value ranges the range 0.0 to 63.992. The valid the measured value ranges from
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 0xFFFE SHOULD be reported measured value is over ranged, the value 0xFFFE SHOULD be reported
to indicate an over-range measurement. If the measurement is to indicate an over-range measurement. If the measurement is
unavailable, the value 0xFFFF SHOULD be reported. Values other unavailable, the value 0xFFFF SHOULD be reported. Values other
than 0xFFFE,0xFFFF and the valid range defined above MUST NOT be than 0xFFFE,0xFFFF and the valid range defined above MUST NOT be
sent and MUST be ignored by the receiving system. sent and MUST be ignored by the receiving system.
3.2.2. Multi-Layer per SSRC Segment 3.2.2. Multi-Channel per SSRC Segment
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1|1| MT |CAlg | SSID |Rsv| MOS Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Segment Type ( S): 1 bit
A one identifies this as either a multi-channel segment or multi-
layer segment.
Media Type (M): 1bit
A one identifies this as a multi-layer video segment.
MoS Type (MT): 4 bits
As defined in Section 3.2.1 of this document. If the value of
this field is not for MoS-V, the receiver using multi-layer
segment should discard this invalid segment with the wrong MoS
Type.
Calculation Algorithm (CALg):3 bits
000~010 - Reserved.
011 - ITU-T P.NAMS [P.NAMS] (Multimedia).
100 - ITU-T P.NBAMS [P.NBAMS] (Multimedia).
101~111 - Reserved for future extension.
Sub Stream Identifier (SSID): 5 bits
If multiple layers of video are carried in the same RTP stream,
each layer will be viewed as a sub stream. Specially, If multiple
views of video are carried in the same RTP stream, each view will
be viewed as a sub stream. This field is used to identify each
layer of video that is carried in the same media stream. NAL unit
type is one example of such SSID.
(Editor's Note: It's not sufficient to simply say that a "NAL unit
type is one example", the draft needs to give normative rules for
the use of this field)
Rsd.:2 bits
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
MUST be ignored by the receiver.
MOS Value: 16 bits
As defined in Section 3.2.1 of this document.
3.2.3. Multi-Channel per SSRC Segment
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1|0| MT |CAlg | CHID | Rsv.| MOS Value | |1|0| MT |CAlg | PT |CHID | MOS Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Segement Type ( S): 1 bit Segement Type ( S): 1 bit
A one identifies this as either a multi-channel segment or multi- A one identifies this as either a multi-channel segment or multi-
layer segment. layer segment.
Media Type (M): 1bit Media Type (M): 1bit
A zero identifies this as a multi-channel per SSRC segment. A zero identifies this as a multi-channel per SSRC segment.
skipping to change at page 11, line 20 skipping to change at page 10, line 13
MoS Type. MoS Type.
Calculation Algorithm (CALg):3 bits Calculation Algorithm (CALg):3 bits
000 - ITU-T P.564 Compliant Algorithm [P.564] (Voice) 000 - ITU-T P.564 Compliant Algorithm [P.564] (Voice)
001 - G.107 [G.107] (Voice) 001 - G.107 [G.107] (Voice)
010 - ETSI TS 101 329-5 Annex E, [ ETSI] (Voice) 010 - ETSI TS 101 329-5 Annex E, [ ETSI] (Voice)
011~100 - Reserved. 011~100 - Reserved.
101~111 - Reserved for future extension. 101~111 - Reserved for future extension.
Channel Identifier (CHID): 4 bits Payload Type (PT): 7 bits
This field is used to identify each channel that is carried in the As defined in Section 3.2.1 of this document.
same media stream. If multiple channels of audio are carried in
one RTP stream, each channel of audio will be viewed as a Channel Identifier (CHID): 3 bits
independent channel(e.g., left channel audio, right channel
audio). Channel mapping follows static ordering rule described in If multiple channels of audio are carried in one RTP stream, each
the section 4.1 of [RFC3551]. channel of audio will be viewed as a independent channel(e.g.,
left channel audio, right channel audio). This field is used to
identify each channel carried in the same media stream. The
default Channel mapping follows static ordering rule described in
the section 4.1 of [RFC3551]. However there are some payload
formats that use different channel mappings, e.g., AC-3 audio over
RTP [RFC4184] only follow AC-3 channel order scheme defined in
[ATSC]. Enhanced AC-3 Audio over RTP [RFC4598] uses dynamic
channel transform mechanism. In order that the appropriate
channel mapping can be determined, QoE reports need to be tied to
an RTP payload format, i.e., including the payload type of the
reported media according to [MONARCH] and using Payload Type to
determine the appropriate channel mapping.
(Editor's Note: It is not clear that the channel mapping in RFC (Editor's Note: It is not clear that the channel mapping in RFC
3551 Section 4.1 is the only one in use) 3551 Section 4.1 is the only one in use)
Rsd.:3 bits Rsd.:3 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
MUST be ignored by the receiver. MUST be ignored by the receiver.
MOS Value: 16 bits MOS Value: 13 bits
As defined in Section 3.2.1 of this document. As defined in Section 3.2.1 of this document.
4. SDP Signaling 4. SDP Signaling
One new parameter is defined for the report block defined in this One new parameter is defined for the report block defined in this
document to be used with Session Description Protocol (SDP) [RFC4566] document to be used with Session Description Protocol (SDP) [RFC4566]
using the Augmented Backus-Naur Form (ABNF) [RFC5234]. It has the using the Augmented Backus-Naur Form (ABNF) [RFC5234]. It has the
following syntax within the "rtcp-xr" attribute [RFC3611]: following syntax within the "rtcp-xr" attribute [RFC3611]:
skipping to change at page 13, line 25 skipping to change at page 12, line 28
to be recorded in decimal. to be recorded in decimal.
o Initial assignments are as follows: o Initial assignments are as follows:
1. ITU-T P.564 Compliant Algorithm [P.564] (Voice) 1. ITU-T P.564 Compliant Algorithm [P.564] (Voice)
2. G.107 [G.107] (Voice) 2. G.107 [G.107] (Voice)
3. ETSI TS 101 329-5 Annex E [ ETSI] (Voice) 3. ETSI TS 101 329-5 Annex E [ ETSI] (Voice)
4. ITU-T P.NAMS [P.NAMS] (Multimedia) 4. ITU-T P.NAMS [P.NAMS] (Multimedia)
5. ITU-T P.NBAMS [P.NBAMS] (Multimedia) 5. ITU-T P.NBAMS [P.NBAMS] (Multimedia)
5.5. New registry of calculation algorithms for multi-layer per SSRC 5.5. New registry of calculation algorithms for multi-channel per SSRC
segment
This document creates a new registry for multi-layer per SSRC segment
defined in the section 3.2.2 to be called "RTCP XR QoE metric block -
layered application Calculation Algorithm" as a sub-registry of the
"RTP Control Protocol Extended Reports (RTCP XR) Block Type Registry"
if multi-layer video are carried in the same RTP stream. Policies
for this new registry are as follows:
o The information required to support this assignment is an
unambiguous definition of the new metric, covering the base
measurements and how they are processed to generate the reported
metric. This should include the units of measurement, how values
of the metric are reported in the one 16-bit fields "MoS Value".
o The review process for the registry is "Specification Required" as
described in Section 4.1 of [RFC5226].
o Entries in the registry are integers. The valid range is 0 to 7
corresponding to the 3-bit field "CAlg" in the block. Values are
to be recorded in decimal.
o Initial assignments are as follows:
1. ITU-T P.NAMS [P.NAMS] (Multimedia)
2. ITU-T P.NBAMS [P.NBAMS] (Multimedia)
5.6. New registry of calculation algorithms for multi-channel per SSRC
segment segment
This document creates a new registry for multi-channel per SSRC This document creates a new registry for multi-channel per SSRC
segment defined in the section 3.2.3 to be called "RTCP XR QoE metric segment defined in the section 3.2.3 to be called "RTCP XR QoE metric
block - multi-channel application Calculation Algorithm" as a sub- block - multi-channel 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" if multi-channel voice data are carried in the Block Type Registry" if multi-channel voice data are carried in the
same RTP stream. Policies for this new registry are as follows: same RTP stream. Policies for this new registry are as follows:
o The information required to support this assignment is an o The information required to support this assignment is an
skipping to change at page 15, line 16 skipping to change at page 13, line 38
The authors would like to thank Alan Clark, Bill Ver Steeg, David R The authors would like to thank Alan Clark, Bill Ver Steeg, David R
Oran, Ali Begen,Colin Perkins, Roni Even,Youqing Yang, Wenxiao Yu and Oran, Ali Begen,Colin Perkins, Roni Even,Youqing Yang, Wenxiao Yu and
Yinliang Hu for their valuable comments and suggestions on this Yinliang Hu for their valuable comments and suggestions on this
document. document.
9. References 9. References
9.1. Normative References 9.1. Normative References
[ATSC] U.S. Advanced Television Systems Committee (ATSC), "ATSC
Standard: Digital Audio Compression (AC-3), Revision B",
ATSC Doc A/52B, June 2005.
[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 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
Applications", RFC 3550, July 2003. Applications", RFC 3550, July 2003.
[RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and [RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and
Video Conferences with Minimal Control", RFC 3551, Video Conferences with Minimal Control", RFC 3551,
July 2003. July 2003.
skipping to change at page 16, line 24 skipping to change at page 15, line 5
Recommendation P.NAMS, November 2009. Recommendation P.NAMS, November 2009.
[P.NBAMS] ITU-T, "non-intrusive bit-stream model for assessment of [P.NBAMS] ITU-T, "non-intrusive bit-stream model for assessment of
performance of multimedia streaming", ITU-T performance of multimedia streaming", ITU-T
Recommendation P.NBAMS, November 2009. Recommendation P.NBAMS, November 2009.
[PMOL] Clark, A. and B. Claise, "Framework for Performance Metric [PMOL] Clark, A. and B. Claise, "Framework for Performance Metric
Development", ID draft-ietf-pmol-metrics-framework-12, Development", ID draft-ietf-pmol-metrics-framework-12,
July 2011. July 2011.
[RFC4184] Link, B., Hager, T., and J. Flaks, "RTP Payload Format for
AC-3 Audio", RFC 4184, October 2005.
[RFC4598] Link, B., "Real-time Transport Protocol (RTP) Payload
Format for Enhanced AC-3 (E-AC-3) Audio", RFC 4598,
July 2006.
Appendix A. Change Log Appendix A. Change Log
A.1. draft-ietf-xrblock-rtcp-xr-qoe-00 A.1. draft-ietf-xrblock-rtcp-xr-qoe-01
The following are the major changes compared to previous version:
o Remove layered support from the QoE metric draft.
o Allocate 7 bits in the block header for payload type to indicate
what type of payload format is in use and add associated
definition of payload type.
o Clarify using Payload Type to determine the appropriate channel
mapping in the definition of Channel Identifier.
A.2. 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
Geoff Hunt Geoff Hunt
Unaffiliated Unaffiliated
 End of changes. 22 change blocks. 
145 lines changed or deleted 105 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/