idnits 2.17.1 draft-ietf-avt-rtcp-xr-jb-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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 seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 25, 2009) is 5536 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 293, but no explicit reference was found in the text -- No information found for draft-ietf-avt-rtcp-xr-measid - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'MEASIDENT' ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) == Outdated reference: A later version (-12) exists of draft-ietf-pmol-metrics-framework-00 Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Audio/Video Transport Working G. Hunt 3 Group BT 4 Internet-Draft A. Clark 5 Intended status: Standards Track Telchemy 6 Expires: August 29, 2009 February 25, 2009 8 RTCP XR Report Block for Jitter Buffer Metric Reporting 9 draft-ietf-avt-rtcp-xr-jb-01.txt 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on August 29, 2009. 34 Copyright Notice 36 Copyright (c) 2009 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents in effect on the date of 41 publication of this document (http://trustee.ietf.org/license-info). 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. 45 Abstract 47 This document defines an RTCP XR Report Block that allows the 48 reporting of Jitter Buffer metrics for a range of RTP applications. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.1. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . 3 54 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 55 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 56 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 4 58 2.1. Report Block Structure . . . . . . . . . . . . . . . . . . 4 59 2.2. Definition of Fields in Jitter Buffer Metrics Block . . . 4 60 3. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 61 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 62 4.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8 63 4.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8 64 4.3. Contact information for registrations . . . . . . . . . . 8 65 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 66 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 10 67 7. Changes since previous version . . . . . . . . . . . . . . . . 11 68 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 69 8.1. Normative References . . . . . . . . . . . . . . . . . . . 12 70 8.2. Informative References . . . . . . . . . . . . . . . . . . 12 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 73 1. Introduction 75 1.1. Jitter Buffer Metrics Block 77 This draft defines a new block type to augment those defined in 78 [RFC3611], for use in a range of RTP applications. 80 The new block type provides information on jitter buffer 81 configuration and performance. 83 The metric belongs to the class of transport-related terminal metrics 84 defined in [MONARCH] (work in progress). 86 Instances of this Metrics Block refer by tag to the separate 87 auxiliary Measurement Identity block [MEASIDENT] which contains 88 information such as the SSRC of the measured stream, and RTP sequence 89 numbers and time intervals indicating the span of the report. 91 1.2. RTCP and RTCP XR Reports 93 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 94 defined an extensible structure for reporting using an RTCP Extended 95 Report (XR). This draft defines a new Extended Report block that 96 MUST be used as defined in [RFC3550] and [RFC3611]. 98 1.3. Performance Metrics Framework 100 The Performance Metrics Framework [PMOLFRAME] provides guidance on 101 the definition and specification of performance metrics. Metrics 102 described in this draft either reference external definitions or 103 define metrics generally in accordance with the guidelines in 104 [PMOLFRAME]. 106 1.4. Applicability 108 These metrics are applicable to a range of RTP applications. 110 2. Jitter Buffer Metrics Block 112 This block describes the configuration and operating parameters of 113 the jitter buffer in the receiver of the RTP end system or RTP mixer 114 which sends the report. 116 2.1. Report Block Structure 118 JB Metrics Block 119 0 1 2 3 120 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 121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 122 | BT=NJB |I| tag |jb cfg | block length=2 | 123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 124 | JB nominal | JB maximum | 125 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 126 | JB high water mark | JB low water mark | 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 Figure 1: Report Block Structure 131 2.2. Definition of Fields in Jitter Buffer Metrics Block 133 block type (BT): 8 bits 135 A Jitter Buffer Metrics Report Block is identified by the constant 136 NJB. 138 [Note to RFC Editor: please replace NJB with the IANA provided RTCP 139 XR block type for this block.] 141 Interval Metric flag (I): 1 bit 143 This field is used to indicate whether the Jitter Buffer Metrics 144 block is an Interval or a Cumulative report, that is, whether the 145 reported values apply to the most recent measurement interval 146 duration between successive metrics reports (I=1) (the Interval 147 Duration) or to the accumulation period characteristic of 148 cumulative measurements (I=0) (the Cumulative Duration). 149 Numerical values for both these intervals are provided in the 150 Measurement Identifier block referenced by the tag field below. 152 Measurement Identifier association (tag): 3 bits 154 This field is used to identify the Measurement Identifier block 155 [MEASIDENT] which describes this measurement. The relevant 156 Measurement Identifier block has the same tag value as the Jitter 157 Buffer Metrics block. Note that there may be more than one 158 Measurement Identifier block per RTCP packet. 160 Jitter Buffer Configuration (jb cfg): 4 bits 162 This field is used to identify the jitter buffer method in use at 163 the receiver, according to the following code: 165 bits 014-017 166 0 = Fixed jitter buffer 167 1 = Adaptive jitter buffer 168 Other values reserved 170 block length: 16 bits 172 The length of this report block in 32-bit words, minus one. For 173 the Jitter Buffer block, the block length is equal to 2. 175 jitter buffer nominal delay (JB nominal): 16 bits 177 This is the current nominal jitter buffer delay in milliseconds, 178 which corresponds to the nominal jitter buffer delay for packets 179 that arrive exactly on time. This parameter MUST be provided for 180 both fixed and adaptive jitter buffer implementations. 182 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 183 reported to indicate an over-range measurement. If the 184 measurement is unavailable, the value 0xFFFF SHOULD be reported. 186 jitter buffer maximum delay (JB maximum): 16 bits 188 This is the current maximum jitter buffer delay in milliseconds 189 which corresponds to the earliest arriving packet that would not 190 be discarded. In simple queue implementations this may correspond 191 to the nominal size. In adaptive jitter buffer implementations, 192 this value may dynamically. This parameter MUST be provided for 193 both fixed and adaptive jitter buffer implementations. 195 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 196 reported to indicate an over-range measurement. If the 197 measurement is unavailable, the value 0xFFFF SHOULD be reported. 199 jitter buffer high water mark (JB high water mark): 16 bits 200 This is the highest value of the jitter buffer nominal delay which 201 occurred at any time during the reporting interval. 203 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 204 reported to indicate an over-range measurement. If the 205 measurement is unavailable, the value 0xFFFF SHOULD be reported. 207 jitter buffer low water mark (JB low water mark): 16 bits 209 This is the lowest value of the jitter buffer nominal delay which 210 occurred at any time during the reporting interval. 212 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 213 reported to indicate an over-range measurement. If the 214 measurement is unavailable, the value 0xFFFF SHOULD be reported. 216 3. SDP Signaling 218 [RFC3611] defines the use of SDP (Session Description Protocol) 219 [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used 220 without prior signaling. 222 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 223 in [RFC3611] by providing an additional value of "xr-format" to 224 signal the use of the report block defined in this document. 226 rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF 228 (defined in [RFC3611]) 230 xr-format = xr-format / xr-jb-block 232 xr-jb-block = "jitter-bfr" 234 4. IANA Considerations 236 New block types for RTCP XR are subject to IANA registration. For 237 general guidelines on IANA considerations for RTCP XR, refer to 238 [RFC3611]. 240 4.1. New RTCP XR Block Type value 242 This document assigns the block type value NJB in the IANA "RTCP XR 243 Block Type Registry" to the "JB Metrics Block". 245 [Note to RFC Editor: please replace NJB with the IANA provided RTCP 246 XR block type for this block.] 248 4.2. New RTCP XR SDP Parameter 250 This document also registers a new parameter "jitter-bfr" in the 251 "RTCP XR SDP Parameters Registry". 253 4.3. Contact information for registrations 255 The contact information for the registrations is: 257 Geoff Hunt (geoff.hunt@bt.com) 259 Orion 2 PP3, Adastral Park, Martlesham Heath, Ipswich IP5 3RE, United 260 Kingdom 262 5. Security Considerations 264 It is believed that this proposed RTCP XR report block introduces no 265 new security considerations beyond those described in [RFC3611]. 266 This block does not provide per-packet statistics so the risk to 267 confidentiality documented in Section 7, paragraph 3 of [RFC3611] 268 does not apply. 270 6. Contributors 272 The authors gratefully acknowledge the comments and contributions 273 made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin 274 Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert 275 Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith 276 Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, 277 Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada. 279 7. Changes since previous version 281 Expanded and clarified IANA Considerations section 283 Changed SDP tag for block to "jitter-bfr" 285 8. References 287 8.1. Normative References 289 [MEASIDENT] 290 Hunt, G., "RTCP XR Measurement Identifier Block", 291 ID draft-ietf-avt-rtcp-xr-measid-01, February 2009. 293 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 294 Requirement Levels", RFC 2119, BCP 14, March 1997. 296 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 297 Applications", RFC 3550, July 2003. 299 [RFC3611] Friedman, T., "RTP Control Protocol Extended Reports (RTCP 300 XR)", RFC 3611, November 2003. 302 [RFC4566] Handley, M., "SDP: Session Description Protocol", 303 RFC 4566, July 2006. 305 8.2. Informative References 307 [MONARCH] Hunt, G., "Monitoring Architectures for RTP", 308 ID draft-hunt-avt-monarch-01, August 2008. 310 [PMOLFRAME] 311 Clark, A., "Framework for Performance Metric Development", 312 ID draft-ietf-pmol-metrics-framework-00, July 2008. 314 Authors' Addresses 316 Geoff Hunt 317 BT 318 Orion 2 PP3 319 Adastral Park 320 Martlesham Heath 321 Ipswich, Suffolk IP5 3RE 322 United Kingdom 324 Phone: +44 1473 651704 325 Email: geoff.hunt@bt.com 327 Alan Clark 328 Telchemy Incorporated 329 2905 Premiere Parkway, Suite 280 330 Duluth, GA 30097 331 USA 333 Email: alan.d.clark@telchemy.com