idnits 2.17.1 draft-scholz-ipfix-rtp-audio-quality-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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 9, 2012) is 4310 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-08) exists of draft-wu-xrblock-rtcp-xr-quality-monitoring-06 ** Obsolete normative reference: RFC 5101 (Obsoleted by RFC 7011) ** Obsolete normative reference: RFC 5102 (Obsoleted by RFC 7012) == Outdated reference: A later version (-01) exists of draft-akhter-ipfix-perfmon-00 Summary: 2 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group H. Scholz 3 Internet-Draft VOIPFUTURE GmbH 4 Intended status: Informational July 9, 2012 5 Expires: January 10, 2013 7 RTP Stream Quality Information Export using IPFIX 8 draft-scholz-ipfix-rtp-audio-quality-00 10 Abstract 12 This draft defines a set of Information Elements and matching 13 Templates to convey RTP media stream quality information in IPFIX 14 packets. The Information Elements describe the RTP quality using the 15 R-factor and Mean Opinion score (MOS) for the entire duration of a 16 monitored stream or for a smaller time slice thereof. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on January 10, 2013. 35 Copyright Notice 37 Copyright (c) 2012 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 This document may contain material from IETF Documents or IETF 51 Contributions published or made publicly available before November 52 10, 2008. The person(s) controlling the copyright in some of this 53 material may not have granted the IETF Trust the right to allow 54 modifications of such material outside the IETF Standards Process. 55 Without obtaining an adequate license from the person(s) controlling 56 the copyright in such materials, this document may not be modified 57 outside the IETF Standards Process, and derivative works of it may 58 not be created outside the IETF Standards Process, except to format 59 it for publication as an RFC or to translate it into languages other 60 than English. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 1.1. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 3 66 1.1.1. Quality of Service (QoS) Monitoring . . . . . . . . . 3 67 1.1.2. Service Level Agreement (SLA) . . . . . . . . . . . . 3 68 1.1.3. Troubleshooting . . . . . . . . . . . . . . . . . . . 3 69 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 70 3. MOS measurement . . . . . . . . . . . . . . . . . . . . . . . 4 71 3.1. rtpMOSCAlg . . . . . . . . . . . . . . . . . . . . . . . . 4 72 3.2. rtpMOSClass1 . . . . . . . . . . . . . . . . . . . . . . . 5 73 3.3. rtpMOSClass2 . . . . . . . . . . . . . . . . . . . . . . . 5 74 3.4. rtpMOSClass3 . . . . . . . . . . . . . . . . . . . . . . . 5 75 3.5. rtpMOSClass4 . . . . . . . . . . . . . . . . . . . . . . . 6 76 3.6. rtpMOSClass5 . . . . . . . . . . . . . . . . . . . . . . . 6 77 3.7. rtpMinMOS . . . . . . . . . . . . . . . . . . . . . . . . 6 78 3.8. rtpAvgMOS . . . . . . . . . . . . . . . . . . . . . . . . 7 79 3.9. rtpMaxMOS . . . . . . . . . . . . . . . . . . . . . . . . 7 80 3.10. rtpMinRFactor . . . . . . . . . . . . . . . . . . . . . . 7 81 3.11. rtpAvgRFactor . . . . . . . . . . . . . . . . . . . . . . 7 82 3.12. rtpMaxRFactor . . . . . . . . . . . . . . . . . . . . . . 8 83 4. Recommended Templates . . . . . . . . . . . . . . . . . . . . 8 84 4.1. Entire stream . . . . . . . . . . . . . . . . . . . . . . 8 85 4.2. Time slice . . . . . . . . . . . . . . . . . . . . . . . . 8 86 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 87 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 88 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 89 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 90 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 91 9.1. Normative References . . . . . . . . . . . . . . . . . . . 9 92 9.2. Informative References . . . . . . . . . . . . . . . . . . 9 93 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 95 1. Introduction 97 IPFIX [RFC5101] and [RFC5102] define a framework allowing to export 98 arbitrary data from so called IPFIX exporters. One type of IPFIX 99 exporter may be co-located with Session Initiation Protocol (SIP) 100 [RFC3261] based VoIP entities or passively observe SIP based VoIP 101 calls. The signaling messages can be exported using 102 [I-D.trammell-ipfix-sip-msg] and Real Time Protocol (RTP) [RFC3550] 103 media streams are covered in [I-D.akhter-ipfix-perfmon]. Media 104 quality is out of the scope of both these documents. This document 105 defines a set of additional IPFIX Information Elements (IEs) to 106 describe RTP audio stream quality. 108 1.1. Use Cases 110 RTP stream flow information contained in IPFIX flow records can be 111 used for various tasks such as Quality of Service (QoS) monitoring, 112 Service Level Agreement (SLA) validation and general troubleshooting 113 of VoIP networks. 115 1.1.1. Quality of Service (QoS) Monitoring 117 Aggregated to higher-level metrics the in-depth information provided 118 by the RTP (and optionally SIP) flow records allow service providers 119 to gauge the overall quality of their network in terms of the quality 120 of experience (QoE). On this level an individual call is less 121 important but the overall quality (e.g. amount of minutes meeting 122 certain quality standards) can be used to get a quick overview on the 123 network and service performance. 125 1.1.2. Service Level Agreement (SLA) 127 SLAs are typically used as part of contracts between two network 128 operators. The requirements on the reliability of the data may be 129 higher compared to QoS Monitoring as the failure to meet 130 contractually agreed quality standards often has a direct commercial 131 impact. 133 1.1.3. Troubleshooting 135 An active network component (SIP proxy, B2BUA, media server) may not 136 have the capabilities to store session related information for a long 137 time to facilitate troubleshooting capabilities (e.g. due to missing 138 hard-disk). Such a system or a group of systems may run the metering 139 process and export the data to a collector for processing or 140 troubleshooting purposes. 142 2. Conventions 144 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 145 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 146 document are to be interpreted as described in RFC 2119 [RFC2119]. 148 3. MOS measurement 150 A multitude of Mean Opinion Score (MOS) assessment algorithms have 151 been defined of which only one or few may be available to an IPFIX 152 Metering Process. The quality (i.e. accuracy) of these algorithms 153 varies and has to be noted when transporting MOS values. 155 An IPFIX Metering Process may use these Information Elements to 156 convey information on the duration of the stream in which the quality 157 fell into the respective category as well as the measurement 158 algorithm used to obtain the information. 160 3.1. rtpMOSCAlg 162 The values carried in this IE are taken from the "RTCP XR QoE metric 163 block - Calculation Algorithm" sub-registry of the "RTP Control 164 Protocol Extended Reports (RTCP XR) Block Type Registry" as defined 165 in [I-D.wu-xrblock-rtcp-xr-quality-monitoring]. 167 Even when an algorithm other than G.107 is used the rtpMOSClassN 168 Information Elements use the R-Factor based classes as defined in the 169 G.107 documentation. 171 Description: The calculation algorithm (CAlg) used by the Metering 172 Process to calculate the MOS value. 174 0: undefined: The algorithm is not known/specified. 176 1: ITU-T P.564 178 2: G.107 180 3: G.107 / ETSI TS 101 329-5 Annex E 182 4: ITU-T P.NAMS 184 5: ITU-T P.NBAMS 185 6: RTCP - Real Time Control Protocol (not fefined in registry!) 187 Data Type: unsigned8 189 Data Type Semantics: identifier 191 PEN (provisional): tbd 193 ElementId (provisional): tbd 195 The MOS values calculated are separated into MOS classes based on the 196 ITU-T G.107 classes. 198 3.2. rtpMOSClass1 200 Description: Number of seconds the monitored stream had a MOS 201 quality lower than 3.10 203 Data Type: float32 205 Data Type Semantics: deltaCounter 207 PEN (provisional): tbd 209 ElementId (provisional): tbd 211 3.3. rtpMOSClass2 213 Description: Number of seconds the monitored stream had a MOS 214 quality larger than or equal 3.10 and lower than 3.60 216 Data Type: float32 218 Data Type Semantics: deltaCounter 220 PEN (provisional): tbd 222 ElementId (provisional): tbd 224 3.4. rtpMOSClass3 226 Description: Number of seconds the monitored stream had a MOS 227 quality larger than or equal 3.60 and lower than 4.03 229 Data Type: float32 230 Data Type Semantics: deltaCounter 232 PEN (provisional): tbd 234 ElementId (provisional): tbd 236 3.5. rtpMOSClass4 238 Description: Number of seconds the monitored stream had a MOS 239 quality larger than or equal 4.03 and lower than 4.34 241 Data Type: float32 243 Data Type Semantics: deltaCounter 245 PEN (provisional): tbd 247 ElementId (provisional): tbd 249 3.6. rtpMOSClass5 251 Description: Number of seconds the monitored stream had a MOS 252 quality larger than or equal 4.34 254 Data Type: float32 256 Data Type Semantics: deltaCounter 258 PEN (provisional): tbd 260 ElementId (provisional): tbd 262 3.7. rtpMinMOS 264 Description: Minimum MOS value measured in the monitoring interval. 266 Data Type: float32 268 Data Type Semantics: quantity 270 PEN (provisional): tbd 272 ElementId (provisional): tbd 274 3.8. rtpAvgMOS 276 Description: Average MOS value measured in the monitoring interval. 278 Data Type: float32 280 Data Type Semantics: quantity 282 PEN (provisional): tbd 284 ElementId (provisional): tbd 286 3.9. rtpMaxMOS 288 Description: Maximum MOS value measured in the monitoring interval. 290 Data Type: float32 292 Data Type Semantics: quantity 294 PEN (provisional): tbd 296 ElementId (provisional): tbd 298 3.10. rtpMinRFactor 300 Description: Minimum R-Factor measured in the monitoring interval. 302 Data Type: float32 304 Data Type Semantics: quantity 306 PEN (provisional): tbd 308 ElementId (provisional): tbd 310 3.11. rtpAvgRFactor 312 Description: Average R-Factor measured in the monitoring interval. 314 Data Type: float32 316 Data Type Semantics: quantity 318 PEN (provisional): tbd 319 ElementId (provisional): tbd 321 3.12. rtpMaxRFactor 323 Description: Maximum R-Factor measured in the monitoring interval. 325 Data Type: float32 327 Data Type Semantics: quantity 329 PEN (provisional): tbd 331 ElementId (provisional): tbd 333 4. Recommended Templates 335 The defined RTP stream IPFIX templates must support both IPv4 and 336 IPv6 transport. They need to carry either flow information regarding 337 the entire duration of an RTP stream or specific to a shorter 338 observation interval. 340 The template incorporates IEs from [I-D.akhter-ipfix-perfmon] to 341 describe the RTP stream. 343 In order to correlate the RTP quality information with signaling 344 information (e.g. subscriber IDs) a correlation ID may be added to 345 the template. Note that this ID has yet to be defined and is outside 346 the scope of this document. 348 4.1. Entire stream 350 tbd 352 4.2. Time slice 354 tbd, based on previous template. Split a single RTP stream in three 355 flow records as example including (empty) 'RTP stream ended' flow 356 record. 358 5. Examples 360 tbd 362 6. Acknowledgements 364 tbd 366 7. IANA Considerations 368 tbd 370 8. Security Considerations 372 tbd 374 9. References 376 9.1. Normative References 378 [I-D.wu-xrblock-rtcp-xr-quality-monitoring] 379 Hunt, G., Clark, A., Wu, W., Schott, R., and G. Zorn, 380 "RTCP XR Blocks for QoE metric reporting", 381 draft-wu-xrblock-rtcp-xr-quality-monitoring-06 (work in 382 progress), December 2011. 384 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 385 Requirement Levels", BCP 14, RFC 2119, March 1997. 387 [RFC5101] Claise, B., "Specification of the IP Flow Information 388 Export (IPFIX) Protocol for the Exchange of IP Traffic 389 Flow Information", RFC 5101, January 2008. 391 [RFC5102] Quittek, J., Bryant, S., Claise, B., Aitken, P., and J. 392 Meyer, "Information Model for IP Flow Information Export", 393 RFC 5102, January 2008. 395 9.2. Informative References 397 [I-D.akhter-ipfix-perfmon] 398 Akhter, A., "Information Elements for Flow Performance 399 Measurement", draft-akhter-ipfix-perfmon-00 (work in 400 progress), October 2010. 402 [I-D.trammell-ipfix-sip-msg] 403 Claise, B., Trammell, B., Kaplan, H., and S. Niccolini, 404 "SIP Message Information Export using IPFIX", 405 draft-trammell-ipfix-sip-msg-02 (work in progress), 406 October 2011. 408 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 409 A., Peterson, J., Sparks, R., Handley, M., and E. 410 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 411 June 2002. 413 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 414 Jacobson, "RTP: A Transport Protocol for Real-Time 415 Applications", STD 64, RFC 3550, July 2003. 417 Author's Address 419 Hendrik Scholz 420 VOIPFUTURE GmbH 421 Wendenstrasse 4 422 Hamburg 20097 423 Germany 425 Phone: +49 40 688 900 100 426 Email: hscholz@voipfuture.com 427 URI: http://www.voipfuture.com/