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