idnits 2.17.1 draft-ietf-avt-rtcpxr-audio-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 212. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 223. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 230. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 236. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- 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 (November 2007) is 6007 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: '1' is defined on line 173, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 176, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 180, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force A. Clark 2 Internet-Draft Telchemy Incorporated 3 Expires: 18th May 2008 A. Pendleton 4 Nortel 5 November 2007 7 RTCP XR - Audio Metrics Report Block 8 draft-ietf-avt-rtcpxr-audio-01 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as 20 Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on 18th May 2008. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2007). 39 Abstract 41 This document defines extensions to the RTCP XR extended report 42 packet type blocks to support the performance monitoring of audio 43 streams transmitted using RTP. 45 Clark [Page 1] 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 49 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . 2 50 3. Audio Metrics Report Block . . . . . . . . . . . . . . . . . 2 51 4. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 4 52 5. Security Considerations . . . . . . . . . . . . . . . . . . 4 53 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 4 54 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 55 8. Informative References . . . . . . . . . . . . . . . . . . . 4 56 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 4 57 Intellectual Property and Copyright Statements . . . . . . . 5 59 1. Introduction 61 This draft defines a block type to augment those defined 62 in RFC3611 for use in Quality of Service reporting for audio over IP. 63 The new block type defined in this draft is the IP Audio Metrics 64 Report Block. This is intended to support both the identification of 65 problems affecting performance and the collection of data that may 66 be useful in optimizing system configuration. 68 Audio performance may be measured using zero (no) reference, partial 69 (reduced) reference or full reference. The primary application of 70 this draft is to support the reporting of real-time, in-service 71 performance obtained using a zero or partial reference model however 72 this approach could also be used to support the remote reporting of 73 metrics from a full reference test. 75 2. Definitions 77 3 Audio Metrics Report Block 79 3.1 Block Description 81 0 1 2 3 82 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 83 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 84 | BT=N | Reserved | block length | 85 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 86 | SSRC | 87 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 88 |0 0 0| Program ID | Reserved | 89 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 90 | Measurement Interval (ms) | 91 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 92 | Mean Audio bit rate (bits/sec) | 93 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 95 Clark [Page 2] 96 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 97 | Round Trip Delay | A-V Delay (Video I/F) | 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 99 | Playout Interrupt Count | Mean Playout Interrupt Size | 100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 101 | Audio Playout buffer size | Mean buffer level | 102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 104 3.2 Definition of Metrics 106 3.2.1 Header 107 The header comprises: 108 (i) Block Type for this report block 109 (ii) Reserved (set to 0xFF) 110 (iii) Block length in words (set to 0x0008) 111 (iv) SSRC of the received RTP stream that this report refers to 112 (v) Program ID (PID) for the audio stream (if MPEG Transport 113 encapsulation is used) 114 (vi) Reserved (set to 0xFFFF) 116 3.2.2 Measurement Interval 117 The interval of time over which these metrics were measured, 118 expressed in milliseconds. 120 3.2.3 Mean Audio Bit Rate 121 The average bit rate of the audio stream expressed in bits per 122 second. 124 3.2.4 Round Trip Delay 125 The Round Trip Delay between the originating and terminating ends 126 of this RTP stream, expressed in millseconds. In unicast or 127 multicast applications this parameter may be set to "undefined" 128 (0xFFFF). 130 3.2.5 A-V Delay 131 The relative delay between decoded audio and video streams expressed 132 in milliseconds. 134 3.2.6 Playout Interrupt Count 135 The number of interruptions that occurred during playout, due to 136 either packet loss or buffer underrun. 138 3.2.7 Mean Playout Interrupt Size 139 The mean duration of interruptions in playout expressed in 140 milliseconds. 142 3.2.8 Audio Playout Buffer Size 143 The available playout buffer size, expressed in milliseconds. 145 3.2.9 Mean Buffer Level 146 The mean playout buffer size, expressed in milliseconds. 148 Clark [Page 3] 149 4. Summary 151 This draft defines an RTCP XR block for audio quality reporting. 152 This is intended for in-service monitoring of audio streaming, IPTV 153 and IP videoconferencing services to provide real time performance 154 feedback and support performance management. 156 5. IANA Considerations 158 The block type "mmm" will need to be replaced with an IANA assigned 159 number within those allocated for RTCP XR report blocks (RFC 3611). 161 6. Security Considerations 163 RTCP reports can contain sensitive information since they can provide 164 information about the nature and duration of a session established 165 between two endpoints. As a result, any third party wishing to 166 obtain this information should be properly authenticated and the 167 information transferred securely. 169 7. Acknowledgments 171 8. Informative References 173 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 174 Levels", BCP 14, RFC 2119, March 1997. 176 [2] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, 177 "RTP: A Transport Protocol for Real-Time Applications", STD 64, 178 RFC 3550, July 2003. 180 [3] Friedman, T., Caceres, R. and A. Clark, "RTP Control Protocol 181 Extended Reports (RTCP XR)", RFC 3611, November 2003. 183 Authors' Addresses 185 Alan Clark 186 Telchemy Incorporated 187 2905 Premiere Parkway, Suite 280 188 Duluth, GA 30097 189 Email: alan@telchemy.com 191 Amy Pendleton 192 Nortel 193 2380 Performance Drive 194 Richardson, TX 75081 195 Email: aspen@nortel.com 197 Full Copyright Statement 199 Clark [Page 4] 200 Copyright (C) The IETF Trust (2007). 202 This document is subject to the rights, licenses and restrictions 203 contained in BCP 78, and except as set forth therein, the authors 204 retain all their rights. 206 This document and the information contained herein are provided on an 207 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 208 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 209 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 210 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 211 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 212 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 214 Intellectual Property 216 The IETF takes no position regarding the validity or scope of any 217 Intellectual Property Rights or other rights that might be claimed to 218 pertain to the implementation or use of the technology described in 219 this document or the extent to which any license under such rights 220 might or might not be available; nor does it represent that it has 221 made any independent effort to identify any such rights. Information 222 on the procedures with respect to rights in RFC documents can be 223 found in BCP 78 and BCP 79. 225 Copies of IPR disclosures made to the IETF Secretariat and any 226 assurances of licenses to be made available, or the result of an 227 attempt made to obtain a general license or permission for the use of 228 such proprietary rights by implementers or users of this 229 specification can be obtained from the IETF on-line IPR repository at 230 http://www.ietf.org/ipr. 232 The IETF invites any interested party to bring to its attention any 233 copyrights, patents or patent applications, or other proprietary 234 rights that may cover technology that may be required to implement 235 this standard. Please address the information to the IETF at ietf- 236 ipr@ietf.org. 238 Acknowledgement 240 Funding for the RFC Editor function is provided by the IETF 241 Administrative Support Activity (IASA). 243 Clark [Page 5]