idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-jb-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (May 9, 2012) is 4369 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2119' is defined on line 296, but no explicit reference was found in the text ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) == Outdated reference: A later version (-10) exists of draft-ietf-xrblock-rtcp-xr-meas-identity-06 == Outdated reference: A later version (-22) exists of draft-ietf-avtcore-monarch-12 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Audio/Video Transport Working Group G. Hunt 3 Internet-Draft Unaffiliated 4 Intended status: Standards Track A. Clark 5 Expires: November 10, 2012 Telchemy 6 V. Singh 7 Aalto University 8 Q. Wu 9 Huawei 10 May 9, 2012 12 RTCP XR Report Block for Jitter Buffer Metric Reporting 13 draft-ietf-xrblock-rtcp-xr-jb-00.txt 15 Abstract 17 This document defines an RTCP XR Report Block that allows the 18 reporting of Jitter Buffer metrics for a range of RTP applications. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on November 10, 2012. 37 Copyright Notice 39 Copyright (c) 2012 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 1.1. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . 3 56 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 57 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 58 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 4 60 2.1. Report Block Structure . . . . . . . . . . . . . . . . . . 4 61 2.2. Definition of Fields in Jitter Buffer Metrics Block . . . 4 62 3. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 63 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 64 4.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8 65 4.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8 66 4.3. Contact information for registrations . . . . . . . . . . 8 67 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 68 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 70 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 71 7.2. Informative References . . . . . . . . . . . . . . . . . . 11 72 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 12 73 A.1. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 12 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 76 1. Introduction 78 1.1. Jitter Buffer Metrics Block 80 This draft defines a new block type to augment those defined in 81 [RFC3611], for use in a range of RTP applications. 83 The new block type provides information on jitter buffer 84 configuration and performance. 86 The metric belongs to the class of transport-related terminal metrics 87 defined in [MONARCH] (work in progress). 89 Instances of this Metrics Block refer by SSRC to the separate 90 auxiliary Measurement Information block [MEASI] which contains 91 information such as the SSRC of the measured stream, and RTP sequence 92 numbers and time intervals indicating the span of the report. 94 1.2. RTCP and RTCP XR Reports 96 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 97 defined an extensible structure for reporting using an RTCP Extended 98 Report (XR). This draft defines a new Extended Report block that 99 MUST be used as defined in [RFC3550] and [RFC3611]. 101 1.3. Performance Metrics Framework 103 The Performance Metrics Framework [RFC6390] provides guidance on the 104 definition and specification of performance metrics. The RTP 105 Monitoring Architectures [MONARCH] provides guideline for reporting 106 block format using RTCP XR. Metrics described in this draft are in 107 accordance with the guidelines in [RFC6390][MONARCH]. 109 1.4. Applicability 111 These metrics are applicable to a range of RTP applications. 113 2. Jitter Buffer Metrics Block 115 This block describes the configuration and operating parameters of 116 the jitter buffer in the receiver of the RTP end system or RTP mixer 117 which sends the report. Instances of this Metrics Block refer by 118 SSRC to the separate auxiliary Measurement Information block [MEASI] 119 which contains measurement intervals. This metric block relies on 120 the measurement interval in the Measurement Information block 121 indicating the span of the report and should be sent in the same 122 compound RTCP packet as the measurement information block. If the 123 measurement interval is not received in the same compound RTCP packet 124 as this metric block, this metric block should be discarded. 126 2.1. Report Block Structure 128 JB Metrics Block 130 0 1 2 3 131 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 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 | BT=NJB | I |jb cfg |rsv| block length=3 | 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 | SSRC of Source | 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 137 | JB nominal | JB maximum | 138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 | JB high water mark | JB low water mark | 140 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 Figure 1: Report Block Structure 144 2.2. Definition of Fields in Jitter Buffer Metrics Block 146 Block type (BT): 8 bits 148 A Jitter Buffer Metrics Report Block is identified by the constant 149 NJB. 151 [Note to RFC Editor: please replace NJB with the IANA provided 152 RTCP XR block type for this block.] 154 Interval Metric flag (I): 2 bits 156 This field is used to indicate whether the Jitter Buffer metrics 157 are Sampled, Interval or Cumulative metrics, that is, whether the 158 reported values applies to the most recent measurement interval 159 duration between successive metrics reports (I=10) (the Interval 160 Duration) or to the accumulation period characteristic of 161 cumulative measurements (I=11) (the Cumulative Duration) or is a 162 sampled instantaneous value (I=01) (Sampled Value). 164 Jitter Buffer Configuration (jb cfg): 4 bits 166 This field is used to identify the jitter buffer method in use at 167 the receiver, according to the following code: 169 bits 014-011 171 0 = Fixed jitter buffer 173 1 = Adaptive jitter buffer 175 Other values reserved 177 Reserved (resv): 2 bits 179 These bits are reserved. They SHOULD be set to zero by senders 180 and MUST be ignored by receivers. 182 block length: 16 bits 184 The length of this report block in 32-bit words, minus one. For 185 the Delay block, the block length is equal to 3. 187 jitter buffer nominal delay (JB nominal): 16 bits 189 This is the current nominal jitter buffer delay in milliseconds, 190 which corresponds to the nominal jitter buffer delay for packets 191 that arrive exactly on time. This parameter MUST be provided for 192 both fixed and adaptive jitter buffer implementations. 194 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 195 reported to indicate an over-range measurement. If the 196 measurement is unavailable, the value 0xFFFF SHOULD be reported. 198 jitter buffer maximum delay (JB maximum): 16 bits 200 This is the current maximum jitter buffer delay in milliseconds 201 which corresponds to the earliest arriving packet that would not 202 be discarded. In simple queue implementations this may correspond 203 to the nominal size. In adaptive jitter buffer implementations, 204 this value may dynamically. This parameter MUST be provided for 205 both fixed and adaptive jitter buffer implementations. 207 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 208 reported to indicate an over-range measurement. If the 209 measurement is unavailable, the value 0xFFFF SHOULD be reported. 211 jitter buffer high water mark (JB high water mark): 16 bits 213 This is the highest value of the jitter buffer nominal delay which 214 occurred at any time during the reporting interval. 216 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 217 reported to indicate an over-range measurement. If the 218 measurement is unavailable, the value 0xFFFF SHOULD be reported. 220 jitter buffer low water mark (JB low water mark): 16 bits 222 This is the lowest value of the jitter buffer nominal delay which 223 occurred at any time during the reporting interval. 225 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 226 reported to indicate an over-range measurement. If the 227 measurement is unavailable, the value 0xFFFF SHOULD be reported. 229 3. SDP Signaling 231 [RFC3611] defines the use of SDP (Session Description Protocol) 232 [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used 233 without prior signaling. 235 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 236 in [RFC3611] by providing an additional value of "xr-format" to 237 signal the use of the report block defined in this document. 239 rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF 241 (defined in [RFC3611]) 243 xr-format =/ xr-jb-block 245 xr-jb-block = "jitter-bfr" 247 4. IANA Considerations 249 New block types for RTCP XR are subject to IANA registration. For 250 general guidelines on IANA considerations for RTCP XR, refer to 251 [RFC3611]. 253 4.1. New RTCP XR Block Type value 255 This document assigns the block type value NJB in the IANA "RTCP XR 256 Block Type Registry" to the "JB Metrics Block". 258 [Note to RFC Editor: please replace NJB with the IANA provided RTCP 259 XR block type for this block.] 261 4.2. New RTCP XR SDP Parameter 263 This document also registers a new parameter "jitter-bfr" in the 264 "RTCP XR SDP Parameters Registry". 266 4.3. Contact information for registrations 268 The contact information for the registrations is: 270 Geoff Hunt (r.geoff.hunt@gmail.com) 272 Orion 2 PP3, Adastral Park, Martlesham Heath, Ipswich IP5 3RE, United 273 Kingdom 275 5. Security Considerations 277 It is believed that this proposed RTCP XR report block introduces no 278 new security considerations beyond those described in [RFC3611]. 279 This block does not provide per-packet statistics so the risk to 280 confidentiality documented in Section 7, paragraph 3 of [RFC3611] 281 does not apply. 283 6. Acknowledgments 285 The authors gratefully acknowledge the comments and contributions 286 made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin 287 Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert 288 Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith 289 Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, 290 Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada. 292 7. References 294 7.1. Normative References 296 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 297 Requirement Levels", March 1997. 299 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 300 Applications", RFC 3550, July 2003. 302 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 303 Protocol Extended Reports (RTCP XR)", November 2003. 305 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 306 Description Protocol", July 2006. 308 7.2. Informative References 310 [MEASI] Hunt, G., "Measurement Identity and information Reporting 311 using SDES item and XR Block", 312 ID draft-ietf-xrblock-rtcp-xr-meas-identity-06, 313 April 2012. 315 [MONARCH] Hunt, G., "Monitoring Architectures for RTP", 316 ID draft-ietf-avtcore-monarch-12, April 2012. 318 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 319 Development", RFC 6390, October 2011. 321 Appendix A. Change Log 323 Note to the RFC-Editor: please remove this section prior to 324 publication as an RFC. 326 A.1. draft-ietf-xrblock-rtcp-xr-jb-00 328 The following are the major changes to previous version : 330 o Boilerplate updates. 332 o references updates 334 o allocate 32 bit field in report block for SSRC 336 o Other editorial changes to get alignment with MONARCH draft. 338 Authors' Addresses 340 Geoff Hunt 341 Unaffiliated 343 Email: r.geoff.hunt@gmail.com 345 Alan Clark 346 Telchemy Incorporated 347 2905 Premiere Parkway, Suite 280 348 Duluth, GA 30097 349 USA 351 Email: alan.d.clark@telchemy.com 353 Varun Singh 354 Aalto University 355 Otakaari 5 A 356 Espoo FIN 02150 357 Finland 359 Email: vsingh.ietf@gmail.com 361 Qin Wu 362 Huawei 363 101 Software Avenue, Yuhua District 364 Nanjing, Jiangsu 210012 365 China 367 Email: sunseawq@huawei.com