idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-meas-identity-07.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 (June 19, 2012) is 4328 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-12 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: December 21, 2012 Telchemy 6 Q. Wu 7 Huawei 8 June 19, 2012 10 Measurement Identity and information Reporting using SDES item and XR 11 Block 12 draft-ietf-xrblock-rtcp-xr-meas-identity-07.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 December 21, 2012. 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-07 . . . . . . . 13 77 A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-06 . . . . . . . 13 78 A.3. draft-ietf-xrblock-xr-rtcp-meas-identity-05 . . . . . . . 13 79 A.4. draft-ietf-xrblock-xr-rtcp-meas-identity-04 . . . . . . . 13 80 A.5. draft-ietf-xrblock-xr-rtcp-meas-identity-03 . . . . . . . 13 81 A.6. draft-ietf-xrblock-xr-rtcp-meas-identity-02 . . . . . . . 13 82 A.7. draft-ietf-xrblock-xr-rtcp-meas-identity-01 . . . . . . . 14 83 A.8. draft-ietf-xrblock-xr-rtcp-meas-identity-00 . . . . . . . 14 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 86 1. Introduction 88 This document defines one new RTP Control Protocol (RTCP) Source 89 Description (SDES) [RFC3550] item, and one new Extended Report (XR) 90 Report Block carrying parameters that identify and describe a 91 measurement period, to which one or more other RTCP XR Report Blocks 92 may refer. 94 The SDES item provides a field for an application specific auxiliary 95 identifier. This identifier may be used to correlate data in XR 96 Blocks within an RTP session with data from a non-RTP session. 98 A RTCP Measurement Identity SDES packet may be associated with a set 99 of RTCP XR metrics blocks which share the same application specific 100 measurement identifier. 102 The XR Report Block does not contain any measurement results 103 (metrics). Instead, it provides information relevant to a 104 measurement reported in one or more other block types, including: 106 o the sequence number of the first packet of the RTP session, 108 o the extended sequence numbers of the first packet of the current 109 measurement interval, and the last packet included in the 110 measurement, 112 o the duration of the most recent measurement interval and 114 o the duration of the interval applicable to cumulative measurements 115 (which may be the duration of the RTP session to date). 117 The method for calculation of the extended RTP sequence number is 118 provide in Real-time Transport Protocol (RTP) [RFC3550]. 120 The RTCP XR Report Block containing the measurement information is 121 intended to provide a single copy of the information necessary to 122 relate measurement data in the RTCP XR blocks to the stream, and 123 measurement period, to which they refer. Commonly, multiple other 124 small metric blocks contain measurement data for the same stream and 125 period, and it would be a large overhead if all of these metric 126 blocks carried duplicated data for measurement identification. 128 The RTCP XR Report Block may be associated with a set of RTCP XR 129 metrics blocks which share the same information relevant to a 130 reported measurement. There may be several such sets in an RTCP 131 packet, in which each set share the same information relevant to a 132 reported measurement. There may also be RTCP XR blocks in the packet 133 which are not associated with a Measurement Information block, for 134 example blocks which were defined before the Measurement Identity and 135 information mechanism was introduced by this document. 137 1.1. RTCP and RTCP XR Reports 139 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 140 defines an extensible structure for reporting using an RTCP Extended 141 Report (XR). This document defines a new Extended Report block that 142 must be used as defined in [RFC3550] and [RFC3611]. 144 1.2. Performance Metrics Framework 146 The Performance Metrics Framework [RFC6390] provides guidance on the 147 definition and specification of performance metrics. The RTP 148 Monitoring Architectures[MONARCH] provides guideline for reporting 149 block format using RTCP XR. The SDES item and XR Block described in 150 this document are in accordance with [RFC6390] and [MONARCH]. 152 1.3. Applicability 154 The RTCP SDES item and the RTCP XR block defined in this document 155 provides information relevant to the measurements for members of a 156 family of RTCP XR metrics blocks which are designed to use it. To 157 use the mechanism defined here, the RTCP XR block containing 158 measurement information is not required to be in the same RTCP packet 159 as the SDES item containing measurement identity. 161 2. Terminology 163 2.1. Standards Language 165 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 166 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 167 document are to be interpreted as described in RFC 2119 [RFC2119]. 169 3. Measurement Identity SDES Item 171 This section defines the format of the Measurement Identity SDES 172 item. The SDES item is carried in the RTCP SDES packet. The packet 173 format for the RTCP SDES is defined in Section 6.5 of [RFC3550]. 174 Each SDES packet is composed of a header with fixed-length fields for 175 version, source count, packet type (PT), and length, followed by zero 176 of more SDES items. In the SDES packet, the PT field is set to SDES 177 (202). 179 3.1. APSI: Application Specific Identifier SDES Item 181 0 1 2 3 182 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 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 | APSI=TBD | length |application specific identifier 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 | .... 187 +-+-+-+-+-+-+-+-+ 189 Application specific identifier is an additional identifier which is 190 useful in the context of a specific application, e.g. an MPEG-2 191 transport identifier [MPEG2]. This item MUST be ignored by 192 applications that are not configured to make use of it. The 193 identifier is variable length. Its length is described by the length 194 field. The value of the length field does not include the two octet 195 SDES item header. If no identifier is provided, the length field 196 MUST be set to zero. 198 4. Measurement Information XR Block 200 4.1. Report Block Structure 202 0 1 2 3 203 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 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | BT=NMI | Reserved | block length = 6 | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | SSRC of stream source | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 | Reserved | first sequence number | 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 211 | extended first sequence number of interval | 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 | extended last sequence number | 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 | Measurement Duration (Cumulative) | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | Measurement Duration (Interval) | 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 Report Block Structure 222 4.2. Definition of Fields in Measurement Information Report Block 224 Block type (BT): 8 bits 226 A Measurement Information Report Block is identified by the 227 constant NMI. 229 [Note to RFC Editor: please replace NMI with the IANA provided 230 RTCP XR block type for this block.] 232 Reserved.: 8 bits 234 These bits are reserved. They MUST be set to zero by senders and 235 ignored by receivers. 237 Block Length: 16 bits 239 The length of this report block in 32-bit words minus one. For 240 the Measurement Information block, the block length is equal to 6. 242 SSRC of source: 32 bits 244 As defined in Section 4.1 of [RFC3611]. 246 Reserved: 16 bits 248 These bits are reserved. They MUST be set to zero by senders and 249 ignored by receivers. 251 First sequence number: 16 bits 253 The RTP sequence number of the first received RTP packet of the 254 session, used to determine the number of packets contributing to 255 cumulative measurements. 257 Extended first sequence number of interval: 32 bits 259 The extended RTP sequence number of the first received RTP packet 260 of the current measurement interval. The extended sequence number 261 is expressed as the low 16 bits value containing the sequence 262 number received in an RTP data packet and the most significant 16 263 bits value containing the corresponding count of sequence number 264 cycles. For additional information on extended sequence numbers 265 see "extended highest sequence number received" definition in RFC 266 3550 section 6.4.1 and RFC 3550 Appendix A.1. 268 Extended last sequence number: 32 bits 270 The extended RTP sequence number of the last received RTP packet 271 which contributed to this measurement. The extended sequence 272 number is expressed as the low 16 bits value containing the 273 sequence number received in an RTP data packet and the most 274 significant 16 bits value containing the corresponding count of 275 sequence number cycles. For additional information on extended 276 sequence numbers see "extended highest sequence number received" 277 definition in RFC 3550 section 6.4.1 and RFC 3550 Appendix A.1. 279 Measurement Duration (Cumulative) : 32 bits 281 The duration, expressed in units of 1/65536 seconds, of the 282 reporting interval applicable to Cumulative reports which use this 283 Measurement Information block. The value of this field can be 284 calculated by the receiver of the RTP media stream, for example, 285 based on received RTP media packets or using RTCP method described 286 in [RFC3550]. 288 Measurement Duration (Interval) : 32 bits 290 The duration, expressed in units of 1/65536 seconds, of the 291 reporting interval applicable to Interval reports which use this 292 Measurement Information block . The value of this field can be 293 calculated by the receiver of the RTP media stream, for example, 294 based on received RTP media packets or using RTCP method described 295 in [RFC3550]. 297 5. IANA Considerations 299 New SDES types for RTCP SDES are subject to IANA registration. For 300 general guidelines on IANA considerations for RTCP SDES, refer to 301 [RFC3550]. 303 5.1. New RTCP SDES Type value 305 This document assigns one additional SDES type in the IANA "RTCP XR 306 Block Type Registry" to the Measurement Identity SDES items as 307 follow: 309 abbrev. name value 310 APSI: Application Specific Identifier TBD 312 [Note to RFC Editor: please replace APSI with the IANA provided RTCP 313 SDES type for the SDES item.] 315 5.2. New RTCP XR Block Type value 317 This document assigns the block type value NMI in the IANA "RTCP XR 318 Block Type Registry" to the "Measurement Information Block". 320 [Note to RFC Editor: please replace NMI with the IANA provided RTCP 321 XR block type for this block.] 323 5.3. Contact information for registrations 325 The contact information for the registrations is: 327 Qin Wu (sunseawq@huawei.com) 329 101 Software Avenue, Yuhua District 330 Nanjing, Jiangsu 210012 331 China 333 6. Security Considerations 335 RTCP reports can contain sensitive information, including information 336 about the nature and duration of a session established between two or 337 more endpoints. Therefore, the use of security mechanisms with RTP, 338 as documented in Section 9 of [RFC3550] applies. 340 7. References 342 7.1. Normative References 344 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 345 Requirement Levels", March 1997. 347 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 348 Applications", RFC 3550, July 2003. 350 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 351 Protocol Extended Reports (RTCP XR)", November 2003. 353 7.2. Informative References 355 [MONARCH] Wu, Q., Hunt, G., and P. , "Monitoring Architectures for 356 RTP", ID draft-ietf-avtcore-monarch-12, April 2012. 358 [MPEG2] "ISO/IEC, "Standard 13818-1"", December 2000. 360 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 361 Development", RFC 6390, October 2011. 363 Appendix A. Change Log 365 Note to the RFC-Editor: please remove this section prior to 366 publication as an RFC. 368 A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-07 370 The following are the major changes to 371 draft-ietf-xrblock-xr-rtcp-meas-identity-06: 373 o One more Editorial change. 375 A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-06 377 The following are the major changes to 378 draft-ietf-xrblock-xr-rtcp-meas-identity-05: 380 o Editorial changes. 382 A.3. draft-ietf-xrblock-xr-rtcp-meas-identity-05 384 The following are the major changes to 385 draft-ietf-xrblock-xr-rtcp-meas-identity-04: 387 o Clarify the definition of extended sequence number. 389 A.4. draft-ietf-xrblock-xr-rtcp-meas-identity-04 391 The following are the major changes to 392 draft-ietf-xrblock-xr-rtcp-meas-identity-03: 394 o Change unit of measurement duration from ms to 1/65536 seconds. 396 A.5. draft-ietf-xrblock-xr-rtcp-meas-identity-03 398 The following are the major changes to 399 draft-ietf-xrblock-xr-rtcp-meas-identity-02: 401 o The Editorial changes. 403 A.6. draft-ietf-xrblock-xr-rtcp-meas-identity-02 405 The following are the major changes to 406 draft-ietf-xrblock-xr-rtcp-meas-identity-01: 408 o Relocating information that belong to SDES item and XR Block 409 respectively in the section 1. 411 o Rephrasing the text that describes SDES packet composition. 413 o Rephrasing identifier description. 415 o Other Editorial changes. 417 A.7. draft-ietf-xrblock-xr-rtcp-meas-identity-01 419 The following are the major changes to 420 draft-ietf-xrblock-xr-rtcp-meas-identity-00: 422 o Replace SDES item containing additional measurement information 423 with XR Block. 425 o Add section 2 to describe following RFC2119 language. 427 o Add Section 1.2 to make SDES item and XR Report be compliant with 428 RFC3550 and RFC3611 430 o Add Section 1.3 to make SDES item and XR Report follow Performance 431 Metrics Framework and RTP Monitoring Architecture. 433 o Add section5.2 to register the new RTCP XR Block Type value. 435 o Remove RTCP SDES Type values that are needed. 437 A.8. draft-ietf-xrblock-xr-rtcp-meas-identity-00 439 The following are the major changes to 440 draft-ietf-avt-rtcp-xr-meas-identity-02: 442 o Change the use of SDES item to convey measurement identity instead 443 of XR Block in section 2. 445 o Update references. 447 o Update security section and remove SDP signaling section. 449 Authors' Addresses 451 Geoff Hunt 452 Unaffiliated 454 Email: r.geoff.hunt@gmail.com 456 Alan Clark 457 Telchemy Incorporated 458 2905 Premiere Parkway, Suite 280 459 Duluth, GA 30097 460 USA 462 Email: alan.d.clark@telchemy.com 464 Qin Wu 465 Huawei 466 101 Software Avenue, Yuhua District 467 Nanjing, Jiangsu 210012 468 China 470 Email: sunseawq@huawei.com