draft-ietf-xrblock-rtcp-xr-qoe-07.txt   draft-ietf-xrblock-rtcp-xr-qoe-08.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: November 15, 2013 Huawei Expires: November 28, 2013 Huawei
R. Schott R. Schott
Deutsche Telekom Deutsche Telekom
G. Zorn G. Zorn
Network Zen Network Zen
May 14, 2013 May 27, 2013
RTP Control Protocol (RTCP) Extended Report (XR) Blocks for QoE Metric RTP Control Protocol (RTCP) Extended Report (XR) Blocks for QoE Metric
Reporting Reporting
draft-ietf-xrblock-rtcp-xr-qoe-07 draft-ietf-xrblock-rtcp-xr-qoe-08
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 QoE 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 39 skipping to change at page 1, line 39
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 November 15, 2013. This Internet-Draft will expire on November 28, 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
skipping to change at page 2, line 22 skipping to change at page 2, line 22
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
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 Audio/Video per SSRC Segment . . . . . 7
3.2.2. Multi-Channel audio per SSRC Segment . . . . . . . . . 8 3.2.2. Multi-Channel audio per SSRC Segment . . . . . . . . . 8
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 9 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 9
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 11 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 13 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 13
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 13 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 13
5.3. Contact information for registrations . . . . . . . . . . 13 5.3. Contact information for registrations . . . . . . . . . . 13
5.4. New registry of calculation algorithms . . . . . . . . . . 13 5.4. New registry of calculation algorithms . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 7. Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15 9.1. Normative References . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . . 16 9.2. Informative References . . . . . . . . . . . . . . . . . . 16
Appendix A. Example of User Quality of Experience Evaluation Appendix A. Example of User Quality of Experience Evaluation
for video stream . . . . . . . . . . . . . . . . . . 17 for video stream . . . . . . . . . . . . . . . . . . 17
Appendix B. Metrics represented using RFC6390 Template . . . . . 17 Appendix B. Metrics represented using RFC6390 Template . . . . . 18
Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 20 Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 20
C.1. draft-ietf-xrblock-rtcp-xr-qoe-07 . . . . . . . . . . . . 20 C.1. draft-ietf-xrblock-rtcp-xr-qoe-08 . . . . . . . . . . . . 21
C.2. draft-ietf-xrblock-rtcp-xr-qoe-06 . . . . . . . . . . . . 20 C.2. draft-ietf-xrblock-rtcp-xr-qoe-07 . . . . . . . . . . . . 21
C.3. draft-ietf-xrblock-rtcp-xr-qoe-04 . . . . . . . . . . . . 21 C.3. draft-ietf-xrblock-rtcp-xr-qoe-06 . . . . . . . . . . . . 21
C.4. draft-ietf-xrblock-rtcp-xr-qoe-03 . . . . . . . . . . . . 21 C.4. draft-ietf-xrblock-rtcp-xr-qoe-04 . . . . . . . . . . . . 21
C.5. draft-ietf-xrblock-rtcp-xr-qoe-02 . . . . . . . . . . . . 21 C.5. draft-ietf-xrblock-rtcp-xr-qoe-03 . . . . . . . . . . . . 21
C.6. draft-ietf-xrblock-rtcp-xr-qoe-01 . . . . . . . . . . . . 21 C.6. draft-ietf-xrblock-rtcp-xr-qoe-02 . . . . . . . . . . . . 21
C.7. draft-ietf-xrblock-rtcp-xr-qoe-00 . . . . . . . . . . . . 21 C.7. draft-ietf-xrblock-rtcp-xr-qoe-01 . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 C.8. draft-ietf-xrblock-rtcp-xr-qoe-00 . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
1.1. QoE Metrics Report Block 1.1. QoE 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. several standard metrics.
skipping to change at page 7, line 17 skipping to change at page 7, line 17
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 two segment types defined in this document: single There are two segment types defined in this document: single
stream per SSRC segment, multi-channel audio per SSRC segment. stream Audio/Video per SSRC segment, multi-channel audio per SSRC
Multi-channel audio per SSRC segment is used to deal with the case segment. Multi-channel audio per SSRC segment is used to deal
where Multi-channel audios are carried in one RTP stream while with the case where Multi-channel audios are carried in one RTP
single stream per SSRC segment is used to deal with the case where stream while single stream Audio/Video per SSRC segment is used to
each media stream is identified by SSRC and sent in separate RTP deal with the case where each media stream is identified by SSRC
stream. The leftmost bit of the segment determines its type. If and sent in separate RTP stream. The leftmost bit of the segment
the leftmost bit of the segment is zero, then it is single stream determines its type. If the leftmost bit of the segment is zero,
segment. If the leftmost bit is one, then it is multi-channel then it is single stream segment. If the leftmost bit is one,
audio segment. Note that two segment types can not be present in then it is multi-channel audio segment. Note that two segment
the same metric block. types can not be present in the same metric block.
3.2.1. Single Stream per SSRC Segment 3.2.1. Single Stream Audio/Video per SSRC Segment
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S| CAID | PT | MOS Value | |S| CAID | PT | MOS Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 zero identifies this as a single stream segment. report block. A zero identifies this as a single stream Audio/
Single stream means there is only one media stream carried in one Video per SSRC segment. Single stream means there is only one
RTP stream. The single stream segment can be used to report the media stream carried in one RTP stream. The single stream Audio/
MoS value associated with the media stream identified by SSRC. If Video per SSRC segment can be used to report the MoS value
there are multiple media streams and they want to use the single associated with the media stream identified by SSRC. If there are
stream per SSRC segment to report the MOS value, they should be multiple media streams and they want to use the single stream
carried in the separate RTP streams with each identified by Audio/Video per SSRC segment to report the MOS value, they should
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 QoE 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 segment in the same RTCP XR packet. stream using single stream Audio/Video per SSRC segment in the
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 QoE 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
skipping to change at page 10, line 25 skipping to change at page 10, line 25
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]
/ "TS101_329";ETSI TS 101 329-5 Annex E [ ETSI] / "TS101_329";ETSI TS 101 329-5 Annex E [ ETSI]
/"JJ201_01 ";TTC JJ201.01 [TTC] /"JJ201_01 ";TTC JJ201.01 [TTC]
/"P1201_01";ITU-T P.1201.2 [P.1201.1] /"P1201_01";ITU-T P.1201.2 [P.1201.1]
/"P1201_02";ITU-T P.1201.2 [P.1201.2] /"P1201_02";ITU-T P.1201.2 [P.1201.2]
/"P1202_01";ITU-T P.1202.1 [P.1202.1] /"P1202_01";ITU-T P.1202.1 [P.1202.1]
/"P1202_02";ITU-T P. NBAMS-HR [P.NBAMS-HR] /"P1202_02";ITU-T P. NBAMS-HR [P.NBAMS-HR]
/ non-ws-string / non-ws-string
extentionattributes = mediatype extentionattributes = mosref
/mosreference
/attributes-ext /attributes-ext
mediatype = "a" ;voice mosref = "mosref=" ("l"; lower resolution
/ "v" ;video / "h";higher resolution
/"m" ;multimedia / "lh";both lower resolution and
mosreference = "mosref=" ("0"; lower resolution ;high resolution are supported
/ "1";higher resolution / non-ws-string
/ 1*2DIGIT ) ;Value 2~15 are valid and
;reserved for future use
attributes-ext = non-ws-string attributes-ext = non-ws-string
SP = <Define in RFC5234> SP = <Define in RFC5234>
DIGIT = <as defined in Section 3.4 of [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=extmap:<value> ["/"<direction>] <name> <extensionattributes> a=extmap:<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 = 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).
Note that the syntax element "mosreference" is referred to the media The syntax element "mosref" is referred to the media resolution(e.g.,
resolution(e.g., Narrowband (3.4kHz) Speech and Standard Definition Narrowband (3.4kHz) Speech and Standard Definition (SD) Resolution
(SD) Resolution Video with lower resolution, Wideband (7kHz) Speech Video with lower resolution, Wideband (7kHz) Speech and High
and High Definition (HD) Resolution Video with higher resolution). Definition (HD) Resolution Video with higher resolution). MOS scores
MOS scores reported in the QoE block may vary with the Mos reference; reported in the QoE block may vary with the MoS reference; For
For example MOS values for narrowband, wideband codecs occupy the example MOS values for narrowband, wideband codecs occupy the same
same range but should be reported in different value. For video range but should be reported in different value. For video
application,MoS scores for SD resolution, HD resolution video also application, MoS scores for SD resolution, HD resolution video also
occupy the same ranges and should be reported in different value. occupy the same ranges and 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 may be used in three ways: signaling described above may 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),
skipping to change at page 11, line 44 skipping to change at page 11, line 39
A direction attribute MAY be included in an extmap; without it, the A direction attribute MAY be included in an extmap; without it, the
direction implicitly inherits, of course, from the RTCP stream direction implicitly inherits, of course, from the RTCP stream
direction. direction.
Segment extension, with their directions, may be signaled for an Segment extension, with their directions, may be signaled for an
"inactive" stream. It is an error to use an extension direction "inactive" stream. It is an error to use an extension direction
incompatible with the stream direction (e.g., a "sendonly" attribute incompatible with the stream direction (e.g., a "sendonly" attribute
for a "recvonly" stream). for a "recvonly" stream).
If an segment extension map is offered as "sendrecv", explicitly or If an 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 MAY be included in an extmap; without it, the
mosref implicitly inherits, of course, from the name attribute (e.g.,
P.1201.1 [P.1201.1] indicates lower resolution used while P.1201.2
[P.1201.2] indicates higher resolution used) or payload type carried
in the segment extension (e.g.,EVRC-WB [RFC5188] indicates using
Wideband Codec). However not all payload types or MoS algorithm
names indicates resolution to be used.
If an segment extension is offered as "lh", explicitly, and
asymmetric behavior is desired, the SDP may be modified to modify
mosref attribute value for that segment extension.
If an answerer receives an offer with an mosref attribute value it
doesn't support (e.g.,the answerer only supports "l" and receives
"h"from offerer), the answer should reject the mosref attribute value
offered by the offerer.
If the answerer wishes to reject a mosref attribute offered by the
offerer, it sets identifiers associated with segment extensions in
the answer to the value in the range 4096-4351. The rejected answer
MUST contain 'mosref ' attribute whose value is the value of the SDP
offer.
Local identifiers in the valid range inclusive in an offer or answer Local identifiers in the valid range inclusive in an offer or answer
must not be used more than once per media section. A session update must not be used more than once per media section. A session update
MAY change the direction qualifiers of segment extensions under use. MAY change the direction qualifiers of segment extensions under use.
A session update MAY add or remove segment extension(s). Identifiers A session update MAY add or remove segment extension(s). Identifiers
values in the valid range MUST NOT be altered (remapped). values in the valid range MUST NOT be altered (remapped).
If a party wishes to offer mutually exclusive alternatives, then If a party wishes to offer mutually exclusive alternatives, then
multiple segment extensions with the same identifier in the multiple segment extensions with the same identifier in the
(unusable) range 4096-4351 may be offered; the answerer should select (unusable) range 4096-4351 may be offered; the answerer should select
at most one of the offered extensions with the same identifier, and at most one of the offered extensions with the same identifier, and
skipping to change at page 12, line 34 skipping to change at page 13, line 6
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- a=rtcp-xr:qoe-
metrics=calg:4906=P1201.1m,calg:4906=P1202.1v,calg:4907=G107a metrics=calg:4906=P1201.1l,calg:4906=P1202.1l,calg:4907=G107
The answerer is interested in transmission P.1202.1 only on video, The answerer is interested in transmission P.1202.1 on lower
but doesn't support P.1201.1 at all. It is interested in resolution application, but doesn't support P.1201.1 on lower
transmission G.107 on audio. It therefore adjusts the declarations: resolution application at all. It is interested in transmission
G.107. It therefore adjusts the declarations:
a=rtcp-xr:qoe-metrics=calg:1=P1202.1v, calg:2=G107a a=rtcp-xr:qoe-metrics=calg:1=P1202.1l, 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 "RTCP XR This document assigns the block type value QMB in the IANA "RTCP XR
skipping to change at page 13, line 41 skipping to change at page 14, line 9
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
measurements and how they are processed to generate the reported measurements and how they are processed to generate the reported
metric. This should include the units of measurement, how values metric.
of the metric are reported in the one 16-bit fields or 13-bit
fields "MoS Value".
o The review process for the registry is "Specification Required" as o The review process for the registry is "Specification Required" as
described in Section 4.1 of [RFC5226]. described in Section 4.1 of [RFC5226].
o Entries in the registry are identified by entry name and mapped to o Entries in the registry are identified by entry name and mapped to
the local identifier (CAID) in the segment extension defined in the local identifier (CAID) in the segment extension defined in
section 3.2. section 3.2.
o Registration Template o Registration Template
skipping to change at page 16, line 51 skipping to change at page 17, line 14
application area", ITU-T Recommendation P.NBAMS-HR, application area", ITU-T Recommendation P.NBAMS-HR,
October 2012. October 2012.
[RFC4184] Link, B., Hager, T., and J. Flaks, "RTP Payload Format for [RFC4184] Link, B., Hager, T., and J. Flaks, "RTP Payload Format for
AC-3 Audio", RFC 4184, October 2005. AC-3 Audio", RFC 4184, October 2005.
[RFC4598] Link, B., "Real-time Transport Protocol (RTP) Payload [RFC4598] Link, B., "Real-time Transport Protocol (RTP) Payload
Format for Enhanced AC-3 (E-AC-3) Audio", RFC 4598, Format for Enhanced AC-3 (E-AC-3) Audio", RFC 4598,
July 2006. July 2006.
[RFC5188] Desineni, H. and Q. Xie, "RTP Payload Format for the
Enhanced Variable Rate Wideband Codec (EVRC-WB) and the
Media Subtype Updates for EVRC-B Codec", RFC 5188,
February 2008.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
Development", RFC 6390, October 2011. Development", RFC 6390, October 2011.
[RFC6792] Wu, Q., "Monitoring Architectures for RTP", RFC 6792, [RFC6792] Wu, Q., "Monitoring Architectures for RTP", RFC 6792,
November 2012. November 2012.
[TTC] TTC 201.01 (Japan), "A method for speech quality [TTC] TTC 201.01 (Japan), "A method for speech quality
assessment for Voice over IP". assessment for Voice over IP".
Appendix A. Example of User Quality of Experience Evaluation for video Appendix A. Example of User Quality of Experience Evaluation for video
skipping to change at page 20, line 33 skipping to change at page 21, line 4
* 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-08
C.1. draft-ietf-xrblock-rtcp-xr-qoe-07 The following are the major changes compared to previous version:
o Remove mostype attribute from SDP extension since it can inferred
from payload type.
o Clarify mosref attribute usage in the O/A.
C.2. 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.2. draft-ietf-xrblock-rtcp-xr-qoe-06 C.3. 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.3. draft-ietf-xrblock-rtcp-xr-qoe-04 C.4. 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.4. draft-ietf-xrblock-rtcp-xr-qoe-03 C.5. 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.5. draft-ietf-xrblock-rtcp-xr-qoe-02 C.6. 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.6. draft-ietf-xrblock-rtcp-xr-qoe-01 C.7. 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.7. draft-ietf-xrblock-rtcp-xr-qoe-00 C.8. 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. 35 change blocks. 
72 lines changed or deleted 104 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/