idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-delay-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 date (October 17, 2011) is 4568 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) == Outdated reference: A later version (-22) exists of draft-ietf-avtcore-monarch-04 Summary: 1 error (**), 0 flaws (~~), 2 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: April 19, 2012 Telchemy 6 K. Gross 7 AVA Networks 8 Q. Wu 9 Huawei 10 October 17, 2011 12 RTCP XR Report Block for Delay metric Reporting 13 draft-ietf-xrblock-rtcp-xr-delay-00.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 April 19, 2012. 37 Copyright Notice 39 Copyright (c) 2011 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 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 78 1. Introduction 80 1.1. Packet Delay Metrics Block 82 This draft defines a new block type to augment those defined in 83 [RFC3611] for use in a range of RTP applications. The new block type 84 supports the reporting of the mean, minimum and maximum values of the 85 network round-trip delay between RTP interfaces in peer RTP end 86 systems as measured, for example, using the RTCP method described in 87 [RFC3550]. It also supports reporting of the component of the round- 88 trip delay internal to the local RTP system. 90 The network metrics belong to the class of packet transport delay 91 metrics defined in [MONARCH] (work in progress). 93 1.2. RTCP and RTCP XR Reports 95 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 96 defined an extensible structure for reporting using an RTCP Extended 97 Report (XR). This draft defines a new Extended Report block that 98 MUST be used as defined in [RFC3550] and [RFC3611]. 100 1.3. Performance Metrics Framework 102 The Performance Metrics Framework [PMOLFRAME] provides guidance on 103 the definition and specification of performance metrics. Metrics 104 described in this draft either reference external definitions or 105 define metrics generally in accordance with the guidelines in 106 [PMOLFRAME]. 108 1.4. Applicability 110 These metrics are applicable to a range of RTP applications. 112 2. Terminology 114 2.1. Standards Language 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 118 document are to be interpreted as described in RFC 2119 [RFC2119]. 120 3. Delay Block 122 Metrics in this block report on packet delay in the stream arriving 123 at the RTP system. 125 3.1. Report Block Structure 127 Delay metrics block 129 0 1 2 3 130 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 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | BT=NDEL |I| resv. | block length = 3 | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | SSRC of Source | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Mean Network Round Trip Delay | End System Delay | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | Min Network Round Trip Delay | Max Network Round Trip Delay | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 Figure 1: Report Block Structure 143 3.2. Definition of Fields in Delay Metrics Report Block 145 Block type (BT): 8 bits 147 A Delay Report Block is identified by the constant NDEL. 149 [Note to RFC Editor: please replace NPDV with the IANA provided 150 RTCP XR block type for this block.] 152 Interval Metric flag (I): 1 bit 154 This field is used to indicate whether the Packet Delay Variation 155 metrics block is an Interval or a Cumulative report, that is, 156 whether the reported values apply to the most recent measurement 157 interval duration between successive metrics reports (I=1) (the 158 Interval Duration) or to the accumulation period characteristic of 159 cumulative measurements (I=0) (the Cumulative Duration). 161 Reserved (resv): 7 bits 163 These bits are reserved. They SHOULD be set to zero by senders 164 and MUST be ignored by receivers. 166 block length: 16 bits 168 The length of this report block in 32-bit words, minus one. For 169 the Delay block, the block length is equal to 3. 171 SSRC of source: 32 bits 173 As defined in Section 4.1 of [RFC3611]. 175 Mean Network Round Trip Delay (ms): 16 bits 177 The Mean Network Round Trip Delay is the mean value of the RTP-to- 178 RTP interface round trip delay in ms over the measurement period, 179 typically determined using RTCP SR/RR. 181 If only one measurement of Round Trip Delay is available for the 182 timespan of the report (whether Interval or Cumulative), this 183 single value should be reported as the mean value. 185 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 186 reported to indicate an over-range measurement. If the 187 measurement is unavailable, the value 0xFFFF SHOULD be reported. 189 End System Delay (ms): 16 bits 191 The End System Delay is the internal round trip delay within the 192 reporting endpoint, calculated using the nominal value of the 193 jitter buffer delay plus the accumulation/ encoding and decoding / 194 playout delay associated with the codec being used. 196 If the measured or estimated value exceeds 0xFFFD, the value 197 0xFFFE SHOULD be reported to indicate an over-range measurement. 198 If the measurement is unavailable, the value 0xFFFF SHOULD be 199 reported. 201 Min Network Round Trip Delay (ms): 16 bits 203 The Min Network Round Trip Delay is the minimum value of the RTP- 204 to-RTP interface round trip delay in ms over the measurement 205 period, typically determined using RTCP SR/RR. 207 If only one measurement of Round Trip Delay is available for the 208 timespan of the report (whether Interval or Cumulative), this 209 single value should be reported as the minimum value. 211 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 212 reported to indicate an over-range measurement. If the 213 measurement is unavailable, the value 0xFFFF SHOULD be reported. 215 Max Network Round Trip Delay (ms): 16 bits 217 The Max Network Round Trip Delay is the maximum value of the RTP- 218 to-RTP interface round trip delay in ms over the measurement 219 period, typically determined using RTCP SR/RR. 221 If only one measurement of Round Trip Delay is available for the 222 timespan of the report (whether Interval or Cumulative), this 223 single value should be reported as the maximum value. 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 4. 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-delay-block 245 xr-delay-block ="delay" 247 5. 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 5.1. New RTCP XR Block Type value 255 This document assigns the block type value NDEL in the IANA "RTCP XR 256 Block Type Registry" to the "Delay Metrics Block". 258 [Note to RFC Editor: please replace NDEL with the IANA provided RTCP 259 XR block type for this block.] 261 5.2. New RTCP XR SDP Parameter 263 This document also registers a new parameter "delay" in the "RTCP XR 264 SDP Parameters Registry". 266 5.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 6. 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 7. Contributors 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 8. References 294 8.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 8.2. Informative References 310 [MONARCH] Hunt, G., "Monitoring Architectures for RTP", 311 ID draft-ietf-avtcore-monarch-04, August 2011. 313 [PMOLFRAME] 314 Clark, A. and B. Claise, "Framework for Performance Metric 315 Development", ID draft-ietf-pmol-metrics-framework-12, 316 July 2011. 318 Appendix A. Change Log 320 Note to the RFC-Editor: please remove this section prior to 321 publication as an RFC. 323 A.1. draft-ietf-xrblock-rtcp-xr-delay-00 325 The following are the major changes to previous version : 327 o Changed BNF for SDP following Christian Groves' and Tom Taylor's 328 comments (4th and 5th May 2009). 330 o Updated references. 332 Authors' Addresses 334 Geoff Hunt 335 Unaffiliated 337 Email: r.geoff.hunt@gmail.com 339 Alan Clark 340 Telchemy Incorporated 341 2905 Premiere Parkway, Suite 280 342 Duluth, GA 30097 343 USA 345 Email: alan.d.clark@telchemy.com 347 Kevin Gross 348 AVA Networks 350 Email: kevin.gross@comcast.net 352 Qin Wu 353 Huawei 354 101 Software Avenue, Yuhua District 355 Nanjing, Jiangsu 210012 356 China 358 Email: sunseawq@huawei.com