draft-ietf-xrblock-rtcp-xr-jb-00.txt   draft-ietf-xrblock-rtcp-xr-jb-01.txt 
Audio/Video Transport Working Group G. Hunt Audio/Video Transport Working Group A. Clark
Internet-Draft Unaffiliated Internet-Draft Telchemy
Intended status: Standards Track A. Clark Intended status: Standards Track V. Singh
Expires: November 10, 2012 Telchemy Expires: April 20, 2013 Aalto University
V. Singh
Aalto University
Q. Wu Q. Wu
Huawei Huawei
May 9, 2012 October 17, 2012
RTCP XR Report Block for Jitter Buffer Metric Reporting RTP Control Protocol (RTCP) Extended Report (XR) Block for Jitter Buffer
draft-ietf-xrblock-rtcp-xr-jb-00.txt Metric Reporting
draft-ietf-xrblock-rtcp-xr-jb-01.txt
Abstract Abstract
This document defines an RTCP XR Report Block that allows the This document defines an RTP Control Protocol (RTCP) Extended Report
reporting of Jitter Buffer metrics for a range of RTP applications. (XR) Block that allows the reporting of Jitter Buffer metrics for 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 November 10, 2012. This Internet-Draft will expire on April 20, 2013.
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.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 4 2. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 4
2.1. Report Block Structure . . . . . . . . . . . . . . . . . . 4 2.1. Report Block Structure . . . . . . . . . . . . . . . . . . 4
2.2. Definition of Fields in Jitter Buffer Metrics Block . . . 4 2.2. Definition of Fields in Jitter Buffer Metrics Block . . . 4
3. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 3. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
4.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8 4.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8
4.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8 4.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8
4.3. Contact information for registrations . . . . . . . . . . 8 4.3. Contact information for registrations . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.2. Informative References . . . . . . . . . . . . . . . . . . 11 8.1. Normative References . . . . . . . . . . . . . . . . . . . 12
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 12 8.2. Informative References . . . . . . . . . . . . . . . . . . 12
A.1. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 12 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 A.1. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 13
A.2. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
1.1. Jitter Buffer Metrics Block 1.1. Jitter Buffer Metrics 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 jitter buffer The new block type provides information on jitter buffer
configuration and performance. configuration and performance.
The metric belongs to the class of transport-related terminal metrics The metric belongs to the class of transport-related terminal metrics
defined in [MONARCH] (work in progress). defined in [MONARCH].
Instances of this Metrics Block refer by SSRC to the separate Instances of this Metrics Block refer by SSRC to the separate
auxiliary Measurement Information block [MEASI] which contains auxiliary Measurement Information block [MEASI] which contains
information such as the SSRC of the measured stream, and RTP sequence information such as the SSRC of the measured stream, and RTP sequence
numbers and time intervals indicating the span of the report. numbers and time intervals indicating the span of the report.
1.2. RTCP and RTCP XR Reports 1.2. RTCP and RTCP XR Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defined an extensible structure for reporting using an RTCP Extended defined an extensible structure for reporting using an RTCP Extended
Report (XR). This draft defines a new Extended Report block that Report (XR). This draft defines a new Extended Report block for use
MUST be used as defined in [RFC3550] and [RFC3611]. with [RFC3550] and [RFC3611].
1.3. Performance Metrics Framework 1.3. Performance Metrics Framework
The Performance Metrics Framework [RFC6390] provides guidance on the The Performance Metrics Framework [RFC6390] provides guidance on the
definition and specification of performance metrics. The RTP definition and specification of performance metrics. The RTP
Monitoring Architectures [MONARCH] provides guideline for reporting Monitoring Architectures [MONARCH] 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][MONARCH]. accordance with the guidelines in [RFC6390][MONARCH].
1.4. Applicability 1.4. Applicability
These metrics are applicable to a range of RTP applications. These metrics are applicable to a range of RTP applications.
Editor Note: What the use is for reporting jitter buffer metrics?
2. Jitter Buffer Metrics Block 2. Jitter Buffer Metrics Block
This block describes the configuration and operating parameters of This block describes the configuration and operating parameters of
the jitter buffer in the receiver of the RTP end system or RTP mixer the jitter buffer in the receiver of the RTP end system or RTP mixer
which sends the report. Instances of this Metrics Block refer by which sends the report. Instances of this Metrics Block refer by
SSRC to the separate auxiliary Measurement Information block [MEASI] SSRC to the separate auxiliary Measurement Information block [MEASI]
which contains measurement intervals. This metric block relies on which contains measurement intervals. This metric block relies on
the measurement interval in the Measurement Information block the measurement interval in the Measurement Information block
indicating the span of the report and should be sent in the same indicating the span of the report and should be sent in the same
compound RTCP packet as the measurement information block. If the compound RTCP packet as the measurement information block. If the
measurement interval is not received in the same compound RTCP packet measurement interval is not received in the same compound RTCP packet
as this metric block, this metric block should be discarded. as this metric block, this metric block should be discarded.
2.1. Report Block Structure 2.1. Report Block Structure
JB Metrics Block JB Metrics Block
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 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 |jb cfg |rsv| block length=3 | | BT=NJB | I |jb cfg |rsv| block length=3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| JB nominal | JB maximum | | JB nominal | JB maximum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| JB high water mark | JB low water mark | | JB high water mark | JB low water mark |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 21 skipping to change at page 5, line 21
the receiver, according to the following code: the receiver, according to the following code:
bits 014-011 bits 014-011
0 = Fixed jitter buffer 0 = Fixed jitter buffer
1 = Adaptive jitter buffer 1 = Adaptive jitter buffer
Other values reserved Other values reserved
Reserved (resv): 2 bits Reserved (rsv): 2 bits
These bits are reserved. They SHOULD be set to zero by senders These bits are reserved. They SHOULD be set to zero by senders
and MUST be ignored by receivers. and MUST be ignored by receivers.
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 and
the Delay block, the block length is equal to 3. MUST be set to 3, in accordance with the definition of this field
in [RFC3611]. The block MUST be discarded if the block length is
set to a different value.
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. This parameter MUST be provided for that arrive exactly on time. This parameter MUST be provided for
both fixed and adaptive jitter buffer implementations. both fixed and adaptive jitter buffer implementations.
If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
skipping to change at page 6, line 14 skipping to change at page 6, line 20
to the nominal size. In adaptive jitter buffer implementations, to the nominal size. In adaptive jitter buffer implementations,
this value may dynamically. This parameter MUST be provided for this value may dynamically. This parameter MUST be provided for
both fixed and adaptive jitter buffer implementations. both fixed and adaptive jitter buffer implementations.
If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF SHOULD be reported. measurement is unavailable, the value 0xFFFF SHOULD be reported.
jitter buffer high water mark (JB high water mark): 16 bits jitter buffer high water mark (JB high water mark): 16 bits
This is the highest value of the jitter buffer nominal delay which This is the highest value of the jitter buffer nominal delay in
occurred at any time during the reporting interval. milliseconds which occurred at any time during the reporting
interval.
If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF SHOULD be reported. measurement is unavailable, the value 0xFFFF SHOULD be reported.
jitter buffer low water mark (JB low water mark): 16 bits jitter buffer low water mark (JB low water mark): 16 bits
This is the lowest value of the jitter buffer nominal delay which This is the lowest value of the jitter buffer nominal delay in
occurred at any time during the reporting interval. milliseconds which occurred at any time during the reporting
interval.
If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF SHOULD be reported. measurement is unavailable, the value 0xFFFF SHOULD be reported.
3. SDP Signaling 3. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) [RFC3611] defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of XR blocks. XR blocks MAY be used [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used
without prior signaling. without prior signaling.
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined This section augments the SDP [RFC4566] attribute "rtcp-xr" defined
in [RFC3611] by providing an additional value of "xr-format" to in [RFC3611] by providing an additional value of "xr-format" to
signal the use of the report block defined in this document. signal the use of the report block defined in this document.
rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF
(defined in [RFC3611])
xr-format =/ xr-jb-block xr-format =/ xr-jb-block
xr-jb-block = "jitter-bfr" xr-jb-block = "jitter-bfr"
4. IANA Considerations 4. 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].
skipping to change at page 8, line 26 skipping to change at page 8, line 26
[Note to RFC Editor: please replace NJB with the IANA provided RTCP [Note to RFC Editor: please replace NJB with the IANA provided RTCP
XR block type for this block.] XR block type for this block.]
4.2. New RTCP XR SDP Parameter 4.2. New RTCP XR SDP Parameter
This document also registers a new parameter "jitter-bfr" in the This document also registers a new parameter "jitter-bfr" in the
"RTCP XR SDP Parameters Registry". "RTCP XR SDP Parameters Registry".
4.3. Contact information for registrations 4.3. Contact information for registrations
The contact information for the registrations is: The contact information for the registrations is:
Geoff Hunt (r.geoff.hunt@gmail.com)
Orion 2 PP3, Adastral Park, Martlesham Heath, Ipswich IP5 3RE, United Qin Wu (sunseawq@huawei.com)
Kingdom 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
5. Security Considerations 5. Security Considerations
It is believed that this proposed RTCP XR report block introduces no It is believed that this proposed RTCP XR report block introduces no
new security considerations beyond those described in [RFC3611]. new security considerations beyond those described in [RFC3611].
This block does not provide per-packet statistics so the risk to This block does not provide per-packet statistics so the risk to
confidentiality documented in Section 7, paragraph 3 of [RFC3611] confidentiality documented in Section 7, paragraph 3 of [RFC3611]
does not apply. does not apply.
6. Acknowledgments 6. Contributors
The authors gratefully acknowledge the comments and contributions Geoff Hunt wrote the initial draft of this document.
made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin
Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert
Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith
Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho,
Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada.
7. References 7. Acknowledgments
7.1. Normative References The authors gratefully acknowledge reviews and feedback provided by
Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor,
Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi,
Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz,
Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi
Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", 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.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", November 2003. Protocol Extended Reports (RTCP XR)", November 2003.
[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.
7.2. Informative References 8.2. Informative References
[MEASI] Hunt, G., "Measurement Identity and information Reporting [MEASI] Hunt, G., "Measurement Identity and information Reporting
using SDES item and XR Block", using SDES item and XR Block",
ID draft-ietf-xrblock-rtcp-xr-meas-identity-06, ID draft-ietf-xrblock-rtcp-xr-meas-identity-10,
April 2012. August 2012.
[MONARCH] Hunt, G., "Monitoring Architectures for RTP", [MONARCH] Hunt, G., "Monitoring Architectures for RTP",
ID draft-ietf-avtcore-monarch-12, April 2012. ID draft-ietf-avtcore-monarch-22, September 2012.
[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.
Appendix A. Change Log Appendix A. 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.
A.1. draft-ietf-xrblock-rtcp-xr-jb-00 A.1. draft-ietf-xrblock-rtcp-xr-jb-01
The following are the major changes to previous version :
o Outdated reference update
o Add one Editor notes to ask clarification on the use of reporting
jitter buffer metrics.
o Other Editorial changes.
A.2. 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
Geoff Hunt
Unaffiliated
Email: r.geoff.hunt@gmail.com
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
Email: alan.d.clark@telchemy.com Email: alan.d.clark@telchemy.com
Varun Singh Varun Singh
Aalto University Aalto University
School of Electrical Engineering
Otakaari 5 A Otakaari 5 A
Espoo FIN 02150 Espoo, FIN 02150
Finland Finland
Email: vsingh.ietf@gmail.com Email: varun@comnet.tkk.fi
Qin Wu Qin Wu
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: sunseawq@huawei.com Email: sunseawq@huawei.com
 End of changes. 30 change blocks. 
62 lines changed or deleted 77 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/