idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-meas-identity-09.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 (July 13, 2012) is 4299 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) == Outdated reference: A later version (-22) exists of draft-ietf-avtcore-monarch-17 Summary: 0 errors (**), 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: January 14, 2013 Telchemy 6 Q. Wu 7 Huawei 8 July 13, 2012 10 Measurement Identity and information Reporting using SDES item and XR 11 Block 12 draft-ietf-xrblock-rtcp-xr-meas-identity-09.txt 14 Abstract 16 This document defines an RTP Control Protocol (RTCP) Source 17 Description (SDES) item and an RTCP Extended Report (XR) Block 18 carrying parameters that identify and describe a measurement period, 19 to which one or more other RTCP XR Report Blocks may refer. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on January 14, 2013. 38 Copyright Notice 40 Copyright (c) 2012 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 1.1. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 4 57 1.2. Performance Metrics Framework . . . . . . . . . . . . . . 4 58 1.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 60 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 61 3. Measurement Identity SDES Item . . . . . . . . . . . . . . . . 6 62 3.1. APSI: Application Specific Identifier SDES Item . . . . . 6 63 4. Measurement Information XR Block . . . . . . . . . . . . . . . 7 64 4.1. Report Block Structure . . . . . . . . . . . . . . . . . . 7 65 4.2. Definition of Fields in Measurement Information Report 66 Block . . . . . . . . . . . . . . . . . . . . . . . . . . 7 67 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 68 5.1. New RTCP SDES Type value . . . . . . . . . . . . . . . . . 10 69 5.2. New RTCP XR Block Type value . . . . . . . . . . . . . . . 10 70 5.3. Contact information for registrations . . . . . . . . . . 10 71 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 72 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 73 7.1. Normative References . . . . . . . . . . . . . . . . . . . 12 74 7.2. Informative References . . . . . . . . . . . . . . . . . . 12 75 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 13 76 A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-09 . . . . . . . 13 77 A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-08 . . . . . . . 13 78 A.3. draft-ietf-xrblock-xr-rtcp-meas-identity-07 . . . . . . . 13 79 A.4. draft-ietf-xrblock-xr-rtcp-meas-identity-06 . . . . . . . 13 80 A.5. draft-ietf-xrblock-xr-rtcp-meas-identity-05 . . . . . . . 13 81 A.6. draft-ietf-xrblock-xr-rtcp-meas-identity-04 . . . . . . . 14 82 A.7. draft-ietf-xrblock-xr-rtcp-meas-identity-03 . . . . . . . 14 83 A.8. draft-ietf-xrblock-xr-rtcp-meas-identity-02 . . . . . . . 14 84 A.9. draft-ietf-xrblock-xr-rtcp-meas-identity-01 . . . . . . . 14 85 A.10. draft-ietf-xrblock-xr-rtcp-meas-identity-00 . . . . . . . 15 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 88 1. Introduction 90 This document defines one new RTP Control Protocol (RTCP) Source 91 Description (SDES) [RFC3550] item, and one new Extended Report (XR) 92 Report Block carrying parameters that identify and describe a 93 measurement period, to which one or more other RTCP XR Report Blocks 94 may refer. 96 The SDES item provides a field for an application specific auxiliary 97 identifier. This identifier may be used to correlate data in XR 98 Blocks within an RTP session with data from a non-RTP session. 100 A RTCP Measurement Identity SDES packet may be associated with a set 101 of RTCP XR metrics blocks which share the same application specific 102 measurement identifier. 104 The XR Report Block does not contain any measurement results 105 (metrics). Instead, it provides information relevant to a 106 measurement reported in one or more other block types, including: 108 o the sequence number of the first packet of the RTP session, 110 o the extended sequence numbers of the first packet of the current 111 measurement interval, and the last packet included in the 112 measurement, 114 o the duration of the most recent measurement interval and 116 o the duration of the interval applicable to cumulative measurements 117 (which may be the duration of the RTP session to date). 119 The method for calculation of the extended RTP sequence number is 120 provide in Real-time Transport Protocol (RTP) [RFC3550]. 122 The RTCP XR Report Block containing the measurement information is 123 intended to provide a single copy of the information necessary to 124 relate measurement data in the RTCP XR blocks to the stream, and 125 measurement period, to which they refer. Commonly, multiple other 126 small metric blocks contain measurement data for the same stream and 127 period, and it would be a large overhead if all of these metric 128 blocks carried duplicated data for measurement identification. 130 The RTCP XR Report Block may be associated with a set of RTCP XR 131 metrics blocks which share the same information relevant to a 132 reported measurement. There may be several such sets in an RTCP 133 packet, in which each set share the same information relevant to a 134 reported measurement. There may also be RTCP XR blocks in the packet 135 which are not associated with a Measurement Information block, for 136 example blocks which were defined before the Measurement Identity and 137 information mechanism was introduced by this document. 139 1.1. RTCP and RTCP XR Reports 141 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 142 defines an extensible structure for reporting using an RTCP Extended 143 Report (XR). This document defines a new Extended Report block. The 144 use of Extended Report blocks is defined by [RFC3611]. 146 1.2. Performance Metrics Framework 148 The Performance Metrics Framework [RFC6390] provides guidance on the 149 definition and specification of performance metrics. The RTP 150 Monitoring Architectures[MONARCH] provides guideline for reporting 151 block format using RTCP XR. The SDES item and XR Block described in 152 this document are in accordance with [RFC6390] and [MONARCH]. 154 1.3. Applicability 156 The RTCP SDES item and the RTCP XR block defined in this document 157 provides information relevant to the measurements for members of a 158 family of RTCP XR metrics blocks which are designed to use it. To 159 use the mechanism defined here, the RTCP XR block containing 160 measurement information is not required to be in the same RTCP packet 161 as the SDES item containing measurement identity. 163 2. Terminology 165 2.1. Standards Language 167 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 168 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 169 document are to be interpreted as described in RFC 2119 [RFC2119]. 171 3. Measurement Identity SDES Item 173 This section defines the format of the Measurement Identity SDES 174 item. The SDES item is carried in the RTCP SDES packet. The packet 175 format for the RTCP SDES is defined in Section 6.5 of [RFC3550]. 176 Each SDES packet is composed of a header with fixed-length fields for 177 version, source count, packet type (PT), and length, followed by zero 178 of more SDES items. In the SDES packet, the PT field is set to SDES 179 (202). 181 3.1. APSI: Application Specific Identifier SDES Item 183 0 1 2 3 184 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 | APSI=TBD | length |application specific identifier 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 | .... 189 +-+-+-+-+-+-+-+-+ 191 Application specific identifier is an additional identifier which is 192 useful in the context of a specific application, e.g. an MPEG-2 193 transport identifier [MPEG2]. This item MUST be ignored by 194 applications that are not configured to make use of it. The 195 identifier is variable length. Its length is described by the length 196 field. The value of the length field does not include the two octet 197 SDES item header. 199 4. Measurement Information XR Block 201 4.1. Report Block Structure 203 0 1 2 3 204 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 205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 206 | BT=NMI | Reserved | block length = 7 | 207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 208 | SSRC of stream source | 209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 210 | Reserved | first sequence number | 211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 | extended first sequence number of interval | 213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 | extended last sequence number | 215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 216 | Measurement Duration (Interval) | 217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 | Measurement Duration (Cumulative) - Seconds (bit 0-31) | 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 | Measurement Duration (Cumulative) - Fraction (bit 0-31) | 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 Report Block Structure 225 4.2. Definition of Fields in Measurement Information Report Block 227 Block type (BT): 8 bits 229 A Measurement Information Report Block is identified by the 230 constant NMI. 232 [Note to RFC Editor: please replace NMI with the IANA provided 233 RTCP XR block type for this block.] 235 Reserved.: 8 bits 237 These bits are reserved. They MUST be set to zero by senders and 238 ignored by receivers. 240 Block Length: 16 bits 242 The length of this report block in 32-bit words minus one. For 243 the Measurement Information block, the block length is equal to 7. 245 SSRC of source: 32 bits 247 As defined in Section 4.1 of [RFC3611]. 249 Reserved: 16 bits 251 These bits are reserved. They MUST be set to zero by senders and 252 ignored by receivers. 254 First sequence number: 16 bits 256 The RTP sequence number of the first received RTP packet of the 257 session, used to determine the number of packets contributing to 258 cumulative measurements. 260 Extended first sequence number of interval: 32 bits 262 The extended RTP sequence number of the first received RTP packet 263 of the current measurement interval. The extended sequence number 264 is expressed as the low 16 bits value containing the sequence 265 number received in an RTP data packet and the most significant 16 266 bits value containing the corresponding count of sequence number 267 cycles. For additional information on extended sequence numbers 268 see "extended highest sequence number received" definition in RFC 269 3550 section 6.4.1 and RFC 3550 Appendix A.1. 271 Extended last sequence number: 32 bits 273 The extended RTP sequence number of the last received RTP packet 274 which contributed to this measurement. The extended sequence 275 number is expressed as the low 16 bits value containing the 276 sequence number received in an RTP data packet and the most 277 significant 16 bits value containing the corresponding count of 278 sequence number cycles. For additional information on extended 279 sequence numbers see "extended highest sequence number received" 280 definition in RFC 3550 section 6.4.1 and RFC 3550 Appendix A.1. 282 Measurement Duration (Interval): 32 bits 284 The duration, expressed in units of 1/65536 seconds, of the 285 reporting interval applicable to Interval reports which use this 286 Measurement Information block . The value of this field can be 287 calculated by the receiver of the RTP media stream, for example, 288 based on received RTP media packets or using RTCP method described 289 in [RFC3550]. 291 Measurement Duration (Cumulative): 64 bits 293 The duration of the reporting interval applicable to Cumulative 294 reports which use this Measurement Information block. The value 295 of this field is represented using a 64-bit NTP-format timestamp 296 as defined in [RFC5905], which is 64-bit unsigned fixed-point 297 number with the integer part in the first 32 bits and the 298 fractional part in the last 32 bits. It can be calculated by the 299 receiver of the RTP media stream, for example, based on received 300 RTP media packets or using RTCP method described in [RFC3550]. 302 5. IANA Considerations 304 New SDES types for RTCP SDES are subject to IANA registration. For 305 general guidelines on IANA considerations for RTCP SDES, refer to 306 [RFC3550]. 308 5.1. New RTCP SDES Type value 310 This document assigns one additional SDES type in the IANA "RTCP XR 311 Block Type Registry" to the Measurement Identity SDES items as 312 follow: 314 abbrev. name value 315 APSI: Application Specific Identifier TBD 317 [Note to RFC Editor: please replace APSI with the IANA provided RTCP 318 SDES type for the SDES item.] 320 5.2. New RTCP XR Block Type value 322 This document assigns the block type value NMI in the IANA "RTCP XR 323 Block Type Registry" to the "Measurement Information Block". 325 [Note to RFC Editor: please replace NMI with the IANA provided RTCP 326 XR block type for this block.] 328 5.3. Contact information for registrations 330 The contact information for the registrations is: 332 Qin Wu (sunseawq@huawei.com) 334 101 Software Avenue, Yuhua District 335 Nanjing, Jiangsu 210012 336 China 338 6. Security Considerations 340 RTCP reports can contain sensitive information, including information 341 about the nature and duration of a session established between two or 342 more endpoints. Therefore, the use of security mechanisms with RTP, 343 as documented in Section 9 of [RFC3550] applies. 345 7. References 347 7.1. Normative References 349 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 350 Requirement Levels", March 1997. 352 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 353 Applications", RFC 3550, July 2003. 355 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 356 Protocol Extended Reports (RTCP XR)", November 2003. 358 [RFC5905] Mills, D., Matin, J., Ed., Burbank, J., and W. Kasch, 359 "Network Time Protocol Version 4: Protocol and Algorithms 360 Specification", RFC 5905, June 2010. 362 7.2. Informative References 364 [MONARCH] Wu, Q., Hunt, G., and P. , "Monitoring Architectures for 365 RTP", ID draft-ietf-avtcore-monarch-17, June 2012. 367 [MPEG2] "ISO/IEC, "Standard 13818-1"", December 2000. 369 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 370 Development", RFC 6390, October 2011. 372 Appendix A. Change Log 374 Note to the RFC-Editor: please remove this section prior to 375 publication as an RFC. 377 A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-09 379 The following are the major changes to 380 draft-ietf-xrblock-xr-rtcp-meas-identity-08: 382 o Change header from "Measurement Reporting" to "Measurement 383 Identity and Duration". 385 A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-08 387 The following are the major changes to 388 draft-ietf-xrblock-xr-rtcp-meas-identity-07: 390 o Expand 32-bit measurement interval (cumulative) into 64 bits and 391 use NTP timestamp format. 393 o Delete the last sentence in the sub-section 3.1. 395 o Block length change for consistency. 397 o Other editorial changes. 399 A.3. draft-ietf-xrblock-xr-rtcp-meas-identity-07 401 The following are the major changes to 402 draft-ietf-xrblock-xr-rtcp-meas-identity-06: 404 o One more Editorial change. 406 A.4. draft-ietf-xrblock-xr-rtcp-meas-identity-06 408 The following are the major changes to 409 draft-ietf-xrblock-xr-rtcp-meas-identity-05: 411 o Editorial changes. 413 A.5. draft-ietf-xrblock-xr-rtcp-meas-identity-05 415 The following are the major changes to 416 draft-ietf-xrblock-xr-rtcp-meas-identity-04: 418 o Clarify the definition of extended sequence number. 420 A.6. draft-ietf-xrblock-xr-rtcp-meas-identity-04 422 The following are the major changes to 423 draft-ietf-xrblock-xr-rtcp-meas-identity-03: 425 o Change unit of measurement duration from ms to 1/65536 seconds. 427 A.7. draft-ietf-xrblock-xr-rtcp-meas-identity-03 429 The following are the major changes to 430 draft-ietf-xrblock-xr-rtcp-meas-identity-02: 432 o The Editorial changes. 434 A.8. draft-ietf-xrblock-xr-rtcp-meas-identity-02 436 The following are the major changes to 437 draft-ietf-xrblock-xr-rtcp-meas-identity-01: 439 o Relocating information that belong to SDES item and XR Block 440 respectively in the section 1. 442 o Rephrasing the text that describes SDES packet composition. 444 o Rephrasing identifier description. 446 o Other Editorial changes. 448 A.9. draft-ietf-xrblock-xr-rtcp-meas-identity-01 450 The following are the major changes to 451 draft-ietf-xrblock-xr-rtcp-meas-identity-00: 453 o Replace SDES item containing additional measurement information 454 with XR Block. 456 o Add section 2 to describe following RFC2119 language. 458 o Add Section 1.2 to make SDES item and XR Report be compliant with 459 RFC3550 and RFC3611 461 o Add Section 1.3 to make SDES item and XR Report follow Performance 462 Metrics Framework and RTP Monitoring Architecture. 464 o Add section5.2 to register the new RTCP XR Block Type value. 466 o Remove RTCP SDES Type values that are needed. 468 A.10. draft-ietf-xrblock-xr-rtcp-meas-identity-00 470 The following are the major changes to 471 draft-ietf-avt-rtcp-xr-meas-identity-02: 473 o Change the use of SDES item to convey measurement identity instead 474 of XR Block in section 2. 476 o Update references. 478 o Update security section and remove SDP signaling section. 480 Authors' Addresses 482 Geoff Hunt 483 Unaffiliated 485 Email: r.geoff.hunt@gmail.com 487 Alan Clark 488 Telchemy Incorporated 489 2905 Premiere Parkway, Suite 280 490 Duluth, GA 30097 491 USA 493 Email: alan.d.clark@telchemy.com 495 Qin Wu 496 Huawei 497 101 Software Avenue, Yuhua District 498 Nanjing, Jiangsu 210012 499 China 501 Email: sunseawq@huawei.com