draft-ietf-xrblock-rtcp-xr-jb-11.txt   draft-ietf-xrblock-rtcp-xr-jb-12.txt 
Audio/Video Transport Working Group A. Clark Audio/Video Transport Working Group A. Clark
Internet-Draft Telchemy Internet-Draft Telchemy
Intended status: Standards Track V. Singh Intended status: Standards Track V. Singh
Expires: October 29, 2013 Aalto University Expires: December 19, 2013 Aalto University
Q. Wu Q. Wu
Huawei Huawei
April 27, 2013 June 17, 2013
RTP Control Protocol (RTCP) Extended Report (XR) Block for Jitter Buffer RTP Control Protocol (RTCP) Extended Report (XR) Block for Jitter Buffer
Metric Reporting Metric Reporting
draft-ietf-xrblock-rtcp-xr-jb-11.txt draft-ietf-xrblock-rtcp-xr-jb-12.txt
Abstract Abstract
This document defines an RTP Control Protocol (RTCP) Extended Report This document defines an RTP Control Protocol (RTCP) Extended Report
(XR) Block that allows the reporting of Jitter Buffer metrics for a (XR) Block that allows the reporting of Jitter Buffer metrics for a
range of RTP applications. 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
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 October 29, 2013. This Internet-Draft will expire on December 19, 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 38 skipping to change at page 2, line 38
6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12
6.3. Contact information for registrations . . . . . . . . . . 12 6.3. Contact information for registrations . . . . . . . . . . 12
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
10.1. Normative References . . . . . . . . . . . . . . . . . . . 16 10.1. Normative References . . . . . . . . . . . . . . . . . . . 16
10.2. Informative References . . . . . . . . . . . . . . . . . . 16 10.2. Informative References . . . . . . . . . . . . . . . . . . 16
Appendix A. Metrics represented using RFC6390 Template . . . . . 17 Appendix A. Metrics represented using RFC6390 Template . . . . . 17
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 20 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 20
B.1. draft-ietf-xrblock-rtcp-xr-jb-11 . . . . . . . . . . . . . 20 B.1. draft-ietf-xrblock-rtcp-xr-jb-12 . . . . . . . . . . . . . 20
B.2. draft-ietf-xrblock-rtcp-xr-jb-10 . . . . . . . . . . . . . 20 B.2. draft-ietf-xrblock-rtcp-xr-jb-11 . . . . . . . . . . . . . 20
B.3. draft-ietf-xrblock-rtcp-xr-jb-09 . . . . . . . . . . . . . 20 B.3. draft-ietf-xrblock-rtcp-xr-jb-10 . . . . . . . . . . . . . 20
B.4. draft-ietf-xrblock-rtcp-xr-jb-08 . . . . . . . . . . . . . 20 B.4. draft-ietf-xrblock-rtcp-xr-jb-09 . . . . . . . . . . . . . 20
B.5. draft-ietf-xrblock-rtcp-xr-jb-07 . . . . . . . . . . . . . 20 B.5. draft-ietf-xrblock-rtcp-xr-jb-08 . . . . . . . . . . . . . 20
B.6. draft-ietf-xrblock-rtcp-xr-jb-05 . . . . . . . . . . . . . 20 B.6. draft-ietf-xrblock-rtcp-xr-jb-07 . . . . . . . . . . . . . 20
B.7. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 21 B.7. draft-ietf-xrblock-rtcp-xr-jb-05 . . . . . . . . . . . . . 21
B.8. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 21 B.8. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 21
B.9. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 21 B.9. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 21
B.10. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 21 B.10. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 B.11. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
1.1. Jitter Buffer Metrics Block 1.1. Jitter Buffer Metrics 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 jitter buffer The new block type provides information on jitter buffer
configuration and performance. configuration and performance.
skipping to change at page 3, line 44 skipping to change at page 3, line 44
definition and specification of performance metrics. The RTP definition and specification of performance metrics. The RTP
Monitoring Architectures [RFC6792] provides guideline for reporting Monitoring Architectures [RFC6792] provides guideline for reporting
block format using RTCP XR. Metrics described in this draft are in block format using RTCP XR. Metrics described in this draft are in
accordance with the guidelines in [RFC6390]and [RFC6792]. accordance with the guidelines in [RFC6390]and [RFC6792].
1.4. Applicability 1.4. Applicability
Real-time applications employ a de-jitter buffer [RFC5481] to absorb Real-time applications employ a de-jitter buffer [RFC5481] to absorb
jitter introduced on the path from source to destination. These jitter introduced on the path from source to destination. These
metrics are used to report how the jitter buffer at the receiving end metrics are used to report how the jitter buffer at the receiving end
of RTP stream behaves as a result of jitter in the network and are of RTP stream behaves as a result of jitter in the network; and they
applicable to a range of RTP applications. are applicable to a range of RTP applications.
These metrics are corresponding to terminal related factors that These metrics are corresponding to terminal related factors that
affect real-time application quality and are useful to provide better affect real-time application quality and are useful to provide better
end-user quality of experience (QoE) when these terminal-related end-user quality of experience (QoE) when these terminal-related
factors are used as inputs to calculate QoE metrics [QMB]. factors are used as inputs to calculate QoE metrics [QMB].
2. Terminology 2. Terminology
2.1. Standards Language 2.1. Standards Language
skipping to change at page 5, line 34 skipping to change at page 5, line 34
packets that arrive on time or at their expected arrival time is packets that arrive on time or at their expected arrival time is
known as the Nominal Delay and this is equivalent to the time known as the Nominal Delay and this is equivalent to the time
difference/ buffer size difference between the on-time packets difference/ buffer size difference between the on-time packets
insertion point and the point at which packets are read out. insertion point and the point at which packets are read out.
The reference for the expected arrival time may, for example, be the The reference for the expected arrival time may, for example, be the
first packet in the session or the running average delay. If all first packet in the session or the running average delay. If all
packets arrived at their expected arrival time, then every packet packets arrived at their expected arrival time, then every packet
would be held in the jitter buffer exactly the Nominal Delay. would be held in the jitter buffer exactly the Nominal Delay.
The Jitter Buffer maximum delay is the delay that is applied to an The jitter buffer maximum delay is the delay that is applied to an
earliest arriving packet that is not discarded and corresponds to the earliest arriving packet that is not discarded and corresponds to the
early edge of the jitter buffer time window. early edge of the jitter buffer time window.
3.1. Idealized Jitter Buffer 3.1. Idealized Jitter Buffer
In practice jitter buffer implementations vary considerably however In practice jitter buffer implementations vary considerably however
they should behave in a manner conceptually consistent with an they should behave in a manner conceptually consistent with an
idealized jitter buffer described as follows: idealized jitter buffer described as follows:
(i). Receive the first packet and delay playout by D ms. Keep (i). Receive the first packet and delay playout by D ms. Keep
the RTP timestamp and receive time as a reference. the RTP timestamp and receive time as a reference.
RTP TS[1] RTP TS[1]
receive time[1] receive time[1]
Assume that both are normalized in ticks. Assume that both are normalized in ticks (there are 10 000 ticks
in a millisecond).
(ii). Receive the next packet (ii). Receive the next packet
(iii). Calculate r = RTP TS[n] - RTP TS[1] and t = receive (iii). Calculate r = RTP TS[n] - RTP TS[1] and t = receive
time[n] - receive time[1]. If r = t then the packet arrived on time[n] - receive time[1]. If r == t then the packet arrived on
time. If r < t then the packet arrived late and if r > t then the time. If r < t then the packet arrived late and if r > t then the
packet arrived early. packet arrived early.
(iv). Delay playout of packet by D + (r-t) (iv). Delay playout of packet by D + (r-t)
(v). Go back to (ii) (v). Go back to (ii)
Note that this idealized implementation assumes that the sender's RTP Note that this idealized implementation assumes that the sender's RTP
clock is synchronized to the clock in the receiver which is used to clock is synchronized to the clock in the receiver which is used to
timestamp packet arrivals. If there is no such inherent timestamp packet arrivals. If there is no such inherent
skipping to change at page 7, line 21 skipping to change at page 7, line 21
[RFC6776] which describes the measurement interval in use. This [RFC6776] which describes the measurement interval in use. This
metrics block relies on the measurement interval in the Measurement metrics block relies on the measurement interval in the Measurement
Information Block indicating the span of the report and MUST be sent Information Block indicating the span of the report and MUST be sent
in the same compound RTCP packet as the Measurement Information in the same compound RTCP packet as the Measurement Information
Block. If the measurement interval is not received in the same Block. If the measurement interval is not received in the same
compound RTCP packet as this metrics block, this metrics block MUST compound RTCP packet as this metrics block, this metrics block MUST
be discarded. be discarded.
4.1. Report Block Structure 4.1. Report Block Structure
JB Metrics Block Jitter Buffer (JB) Metrics Block
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=NJB | I |C| Rsvd. | block length=3 | | BT=NJB | I |C| Rsvd. | block length=3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| JB nominal | JB maximum | | JB nominal | JB maximum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 8, line 46 skipping to change at page 8, line 46
The length of this report block in 32-bit words, minus one, in The length of this report block in 32-bit words, minus one, in
accordance with the definition in [RFC3611]. This field MUST be accordance with the definition in [RFC3611]. This field MUST be
set to 3 to match the fixed length of the report block. set to 3 to match the fixed length of the report block.
jitter buffer nominal delay (JB nominal): 16 bits jitter buffer nominal delay (JB nominal): 16 bits
This is the current nominal jitter buffer delay in milliseconds, This is the current nominal jitter buffer delay in milliseconds,
which corresponds to the nominal jitter buffer delay for packets which corresponds to the nominal jitter buffer delay for packets
that arrive exactly on time. It is calculated based on the time that arrive exactly on time. It is calculated based on the time
spend in the jitter buffer for the packet that arrives exactly on spent in the jitter buffer for the packet that arrives exactly on
time. This parameter MUST be provided for both fixed and adaptive time. This parameter MUST be provided for both fixed and adaptive
jitter buffer implementations. jitter buffer implementations.
The measured value is unsigned value. If the measured value The measured value is unsigned value. If the measured value
exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an
over-range measurement. If the measurement is unavailable, the over-range measurement. If the measurement is unavailable, the
value 0xFFFF MUST be reported. value 0xFFFF MUST be reported.
jitter buffer maximum delay (JB maximum): 16 bits jitter buffer maximum delay (JB maximum): 16 bits
skipping to change at page 16, line 32 skipping to change at page 16, line 32
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", July 2006. Description Protocol", July 2006.
[RFC6776] Wu, Q., "Measurement Identity and information Reporting [RFC6776] Wu, Q., "Measurement Identity and information Reporting
using SDES item and XR Block", RFC 6776, August 2012. using SDES item and XR Block", RFC 6776, August 2012.
10.2. Informative References 10.2. Informative References
[QMB] Clark, A., "RTP Control Protocol (RTCP) Extended Report [QMB] Clark, A., "RTP Control Protocol (RTCP) Extended Report
(XR) Blocks for QoE Metric Reporting", (XR) Blocks for QoE Metric Reporting",
ID draft-ietf-xrblock-rtcp-xr-qoe-06, February 2013. ID draft-ietf-xrblock-rtcp-xr-qoe-08, May 2013.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
Applicability Statement", RFC 5481, March 2009. Applicability Statement", RFC 5481, March 2009.
[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.
[RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design
Considerations for Protocol Extensions", RFC 6709, Considerations for Protocol Extensions", RFC 6709,
September 2012. September 2012.
skipping to change at page 20, line 10 skipping to change at page 20, line 10
* 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
Note to the RFC-Editor: please remove this section prior to Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
B.1. draft-ietf-xrblock-rtcp-xr-jb-11 B.1. draft-ietf-xrblock-rtcp-xr-jb-12
The following are the major changes to previous version :
o Editorial changes based on recieved comments.
B.2. draft-ietf-xrblock-rtcp-xr-jb-11
The following are the major changes to previous version : The following are the major changes to previous version :
o Comments in WGLC and from PM-DIR review are addressed in this o Comments in WGLC and from PM-DIR review are addressed in this
version. version.
B.2. draft-ietf-xrblock-rtcp-xr-jb-10 B.3. draft-ietf-xrblock-rtcp-xr-jb-10
The following are the major changes to previous version : The following are the major changes to previous version :
o Add some text to section 3.2 to clarify how fixed jitter buffer is o Add some text to section 3.2 to clarify how fixed jitter buffer is
used. used.
o Other Editorial changes. o Other Editorial changes.
B.3. draft-ietf-xrblock-rtcp-xr-jb-09 B.4. draft-ietf-xrblock-rtcp-xr-jb-09
The following are the major changes to previous version : The following are the major changes to previous version :
o Incorporate proposed changes by Kevin and proposed text by Alan to o Incorporate proposed changes by Kevin and proposed text by Alan to
address interoperability report issue. address interoperability report issue.
o Add new appendix to format metrics using RFC6390 template. o Add new appendix to format metrics using RFC6390 template.
B.4. draft-ietf-xrblock-rtcp-xr-jb-08 B.5. draft-ietf-xrblock-rtcp-xr-jb-08
The following are the major changes to previous version : The following are the major changes to previous version :
o Rewrote descriptive text and definitions for clarification. o Rewrote descriptive text and definitions for clarification.
B.5. draft-ietf-xrblock-rtcp-xr-jb-07 B.6. draft-ietf-xrblock-rtcp-xr-jb-07
The following are the major changes to previous version : The following are the major changes to previous version :
o Add one new section to discuss jitter buffer operation. o Add one new section to discuss jitter buffer operation.
B.6. draft-ietf-xrblock-rtcp-xr-jb-05 B.7. draft-ietf-xrblock-rtcp-xr-jb-05
The following are the major changes to previous version : The following are the major changes to previous version :
o Some editorial change changes based on the discussion with Glen o Some editorial change changes based on the discussion with Glen
and Kevin on the list. and Kevin on the list.
B.7. draft-ietf-xrblock-rtcp-xr-jb-03 B.8. draft-ietf-xrblock-rtcp-xr-jb-03
The following are the major changes to previous version : The following are the major changes to previous version :
o Reduce the "jb cfg" to 1-bit based on discussion in the WGLC. o Reduce the "jb cfg" to 1-bit based on discussion in the WGLC.
o Other editorial change changes aligning with PDV,Delay draft. o Other editorial change changes aligning with PDV,Delay draft.
B.8. draft-ietf-xrblock-rtcp-xr-jb-02 B.9. draft-ietf-xrblock-rtcp-xr-jb-02
The following are the major changes to previous version : The following are the major changes to previous version :
o Add some explanation text in the SDP offer/answer section. o Add some explanation text in the SDP offer/answer section.
o Add some text in applicability section to explain the use to o Add some text in applicability section to explain the use to
report jitter buffer metrics. report jitter buffer metrics.
o Other editorial change changes aligning with PDV,Delay draft. o Other editorial change changes aligning with PDV,Delay draft.
B.9. draft-ietf-xrblock-rtcp-xr-jb-01 B.10. draft-ietf-xrblock-rtcp-xr-jb-01
The following are the major changes to previous version : The following are the major changes to previous version :
o Outdated reference update o Outdated reference update
o Add one Editor notes to ask clarification on the use of reporting o Add one Editor notes to ask clarification on the use of reporting
jitter buffer metrics. jitter buffer metrics.
o Other Editorial changes. o Other Editorial changes.
B.10. draft-ietf-xrblock-rtcp-xr-jb-00 B.11. draft-ietf-xrblock-rtcp-xr-jb-00
The following are the major changes to previous version : The following are the major changes to previous version :
o Boilerplate updates. o Boilerplate updates.
o references updates o references updates
o allocate 32 bit field in report block for SSRC o allocate 32 bit field in report block for SSRC
o Other editorial changes to get alignment with MONARCH draft. o Other editorial changes to get alignment with MONARCH draft.
Authors' Addresses Authors' Addresses
Alan Clark Alan Clark
Telchemy Incorporated Telchemy Incorporated
2905 Premiere Parkway, Suite 280 2905 Premiere Parkway, Suite 280
Duluth, GA 30097 Duluth, GA 30097
USA USA
 End of changes. 23 change blocks. 
34 lines changed or deleted 41 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/