idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-delay-02.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 date (April 6, 2012) is 4401 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) ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) -- No information found for draft-ietf-xrblock-rtcp-xr-measu-identity - is the name correct? == Outdated reference: A later version (-22) exists of draft-ietf-avtcore-monarch-04 Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). 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: October 8, 2012 Telchemy 6 K. Gross 7 AVA Networks 8 Q. Wu 9 Huawei 10 April 6, 2012 12 RTCP XR Report Block for Delay metric Reporting 13 draft-ietf-xrblock-rtcp-xr-delay-02.txt 15 Abstract 17 This document defines an RTCP XR Report Block that allows the 18 reporting of Delay metrics for use in 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 October 8, 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. Packet Delay 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 61 3. Delay Block . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5 63 3.2. Definition of Fields in Delay Metrics Report Block . . . . 5 64 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8 65 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 66 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9 67 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9 68 5.3. Contact information for registrations . . . . . . . . . . 9 69 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 70 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 11 71 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 72 8.1. Normative References . . . . . . . . . . . . . . . . . . . 12 73 8.2. Informative References . . . . . . . . . . . . . . . . . . 12 74 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 13 75 A.1. draft-ietf-xrblock-rtcp-xr-delay-00 . . . . . . . . . . . 13 76 A.2. draft-ietf-xrblock-rtcp-xr-delay-01 . . . . . . . . . . . 13 77 A.3. draft-ietf-xrblock-rtcp-xr-delay-02 . . . . . . . . . . . 13 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 80 1. Introduction 82 1.1. Packet Delay Metrics Block 84 This draft defines a new block type to augment those defined in 85 [RFC3611] for use in a range of RTP applications. The new block type 86 supports the reporting of the mean, minimum and maximum values of the 87 network round-trip delay between RTP interfaces in peer RTP end 88 systems as measured, for example, using the RTCP method described in 89 [RFC3550]. It also supports reporting of the component of the round- 90 trip delay internal to the local RTP system. 92 The network metrics belong to the class of packet transport delay 93 metrics defined in [MONARCH] (work in progress). 95 1.2. RTCP and RTCP XR Reports 97 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 98 defined an extensible structure for reporting using an RTCP Extended 99 Report (XR). This draft defines a new Extended Report block that 100 MUST be used as defined in [RFC3550] and [RFC3611]. 102 1.3. Performance Metrics Framework 104 The Performance Metrics Framework [RFC6390] provides guidance on the 105 definition and specification of performance metrics. Metrics 106 described in this draft either reference external definitions or 107 define metrics generally in accordance with the guidelines in 108 [RFC6390]. 110 1.4. Applicability 112 These metrics are applicable to a range of RTP applications. 114 2. Terminology 116 2.1. Standards Language 118 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 119 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 120 document are to be interpreted as described in RFC 2119 [RFC2119]. 122 3. Delay Block 124 Metrics in this block report on packet delay in the stream arriving 125 at the RTP system. Instances of this Metrics Block refer by SSRC to 126 the separate auxiliary Measurement Information block [MEASI] which 127 contains measurement intervals. This metric block relies on the 128 measurement interval in the Measurement Information block indicating 129 the span of the report. If the measurement interval is not received 130 for this metric block, this metric block should be discarded. 132 3.1. Report Block Structure 134 Delay metrics block 136 0 1 2 3 137 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 138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 | BT=NDEL | I | resv. | block length = 5 | 140 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 | SSRC of Source | 142 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 143 | Mean Network Round Trip Delay | 144 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 145 | End System Delay | 146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 147 | Min Network Round Trip Delay | 148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 149 | Max Network Round Trip Delay | 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 152 Figure 1: Report Block Structure 154 3.2. Definition of Fields in Delay Metrics Report Block 156 Block type (BT): 8 bits 158 A Delay Report Block is identified by the constant NDEL. 160 [Note to RFC Editor: please replace NDEL with the IANA provided 161 RTCP XR block type for this block.] 163 Interval Metric flag (I): 2 bit 165 This field is used to indicate whether the Basic Loss/Discard 166 metrics are sampled, Interval or Cumulative metrics, that is, 167 whether the reported values applies to the most recent measurement 168 interval duration between successive metrics reports (I=10) (the 169 Interval Duration) or to the accumulation period characteristic of 170 cumulative measurements (I=11) (the Cumulative Duration) or to the 171 value of a continuously measured or calculated that has been 172 sampled at end of the interval (I=01) (Sampled Value). 174 Reserved (resv): 6 bits 176 These bits are reserved. They SHOULD be set to zero by senders 177 and MUST be ignored by receivers. 179 block length: 16 bits 181 The length of this report block in 32-bit words, minus one. For 182 the Delay block, the block length is equal to 5. 184 SSRC of source: 32 bits 186 As defined in Section 4.1 of [RFC3611]. 188 Mean Network Round Trip Delay: 32 bits 190 The Mean Network Round Trip Delay is the mean value of the RTP-to- 191 RTP interface round trip delay over the measurement period, 192 expressed in units of 1/65536 seconds. This value is typically 193 determined using RTCP SR/RR. 195 If only one measurement of Round Trip Delay is available for the 196 timespan of the report (whether Interval or Cumulative), this 197 single value should be reported as the mean value. 199 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 200 reported to indicate an over-range measurement. If the 201 measurement is unavailable, the value 0xFFFF SHOULD be reported. 203 End System Delay: 32 bits 205 The End System Delay is the internal round trip delay within the 206 reporting endpoint, expressed in units of 1/65536 seconds. This 207 value is calculated using the nominal value of the jitter buffer 208 delay plus the accumulation/ encoding and decoding / playout delay 209 associated with the codec being used. 211 If the measured or estimated value exceeds 0xFFFD, the value 212 0xFFFE SHOULD be reported to indicate an over-range measurement. 213 If the measurement is unavailable, the value 0xFFFF SHOULD be 214 reported. 216 Min Network Round Trip Delay: 32 bits 218 The Min Network Round Trip Delay is the minimum value of the RTP- 219 to-RTP interface round trip delay over the measurement period, 220 expressed in units of 1/65536 seconds. This value is typically 221 determined using RTCP SR/RR. 223 If only one measurement of Round Trip Delay is available for the 224 timespan of the report (whether Interval or Cumulative), this 225 single value should be reported as the minimum value. 227 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 228 reported to indicate an over-range measurement. If the 229 measurement is unavailable, the value 0xFFFF SHOULD be reported. 231 Max Network Round Trip Delay: 32 bits 233 The Max Network Round Trip Delay is the maximum value of the RTP- 234 to-RTP interface round trip delay over the measurement period, 235 expressed in units of 1/65536 seconds. This value is typically 236 determined using RTCP SR/RR. 238 If only one measurement of Round Trip Delay is available for the 239 timespan of the report (whether Interval or Cumulative), this 240 single value should be reported as the maximum value. 242 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 243 reported to indicate an over-range measurement. If the 244 measurement is unavailable, the value 0xFFFF SHOULD be reported. 246 4. SDP Signaling 248 [RFC3611] defines the use of SDP (Session Description Protocol) 249 [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used 250 without prior signaling. 252 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 253 in [RFC3611] by providing an additional value of "xr-format" to 254 signal the use of the report block defined in this document. 256 rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF 258 (defined in [RFC3611]) 260 xr-format =/ xr-delay-block 262 xr-delay-block ="delay" 264 5. IANA Considerations 266 New block types for RTCP XR are subject to IANA registration. For 267 general guidelines on IANA considerations for RTCP XR, refer to 268 [RFC3611]. 270 5.1. New RTCP XR Block Type value 272 This document assigns the block type value NDEL in the IANA "RTCP XR 273 Block Type Registry" to the "Delay Metrics Block". 275 [Note to RFC Editor: please replace NDEL with the IANA provided RTCP 276 XR block type for this block.] 278 5.2. New RTCP XR SDP Parameter 280 This document also registers a new parameter "delay" in the "RTCP XR 281 SDP Parameters Registry". 283 5.3. Contact information for registrations 285 The contact information for the registrations is: 287 Geoff Hunt (r.geoff.hunt@gmail.com) 289 Orion 2 PP3, Adastral Park, Martlesham Heath, Ipswich IP5 3RE, United 290 Kingdom 292 6. Security Considerations 294 It is believed that this proposed RTCP XR report block introduces no 295 new security considerations beyond those described in [RFC3611]. 296 This block does not provide per-packet statistics so the risk to 297 confidentiality documented in Section 7, paragraph 3 of [RFC3611] 298 does not apply. 300 7. Contributors 302 The authors gratefully acknowledge the comments and contributions 303 made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin 304 Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert 305 Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith 306 Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, 307 Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada. 309 8. References 311 8.1. Normative References 313 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 314 Requirement Levels", March 1997. 316 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 317 Applications", RFC 3550, July 2003. 319 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 320 Protocol Extended Reports (RTCP XR)", November 2003. 322 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 323 Description Protocol", July 2006. 325 8.2. Informative References 327 [MEASI] Hunt, G., "Measurement Identity and information Reporting 328 using SDES item and XR Block", 329 ID draft-ietf-xrblock-rtcp-xr-measu-identity-01, 330 October 2011. 332 [MONARCH] Hunt, G., "Monitoring Architectures for RTP", 333 ID draft-ietf-avtcore-monarch-04, August 2011. 335 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 336 Development", RFC 6390, October 2011. 338 Appendix A. Change Log 340 Note to the RFC-Editor: please remove this section prior to 341 publication as an RFC. 343 A.1. draft-ietf-xrblock-rtcp-xr-delay-00 345 The following are the major changes to previous version : 347 o Changed BNF for SDP following Christian Groves' and Tom Taylor's 348 comments (4th and 5th May 2009). 350 o Updated references. 352 A.2. draft-ietf-xrblock-rtcp-xr-delay-01 354 The following are the major changes to previous version : 356 o Updated references. 358 o Allocate one more bit for Interval metric flag to indicate sampled 359 metric can be used. 361 o add a few clarification text for failure mode. 363 A.3. draft-ietf-xrblock-rtcp-xr-delay-02 365 The following are the major changes to previous version : 367 o Allocate 32bits for each metrics and change unit for each metric 368 from ms to 1/65536 seconds. 370 Authors' Addresses 372 Geoff Hunt 373 Unaffiliated 375 Email: r.geoff.hunt@gmail.com 377 Alan Clark 378 Telchemy Incorporated 379 2905 Premiere Parkway, Suite 280 380 Duluth, GA 30097 381 USA 383 Email: alan.d.clark@telchemy.com 385 Kevin Gross 386 AVA Networks 388 Email: kevin.gross@avanw.com 390 Qin Wu 391 Huawei 392 101 Software Avenue, Yuhua District 393 Nanjing, Jiangsu 210012 394 China 396 Email: sunseawq@huawei.com