idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-meas-identity-04.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 seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (April 10, 2012) is 4396 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 (~~), 3 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 12, 2012 Telchemy 6 Q. Wu 7 Huawei 8 April 10, 2012 10 Measurement Identity and information Reporting using SDES item and XR 11 Block 12 draft-ietf-xrblock-rtcp-xr-meas-identity-04.txt 14 Abstract 16 This document defines an RTCP SDES item and an RTCP XR Block carrying 17 parameters that identify and describe a measurement period, to which 18 one or more other RTCP XR Report Blocks may refer. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on October 12, 2012. 37 Copyright Notice 39 Copyright (c) 2012 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 1.1. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 4 56 1.2. Performance Metrics Framework . . . . . . . . . . . . . . 4 57 1.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 60 3. Measurement Identity SDES Item . . . . . . . . . . . . . . . . 6 61 3.1. APSI: Application Specific Identifier SDES Item . . . . . 6 62 4. Measurement Information XR Block . . . . . . . . . . . . . . . 7 63 4.1. Report Block Structure . . . . . . . . . . . . . . . . . . 7 64 4.2. Definition of Fields in Measurement Information Report 65 Block . . . . . . . . . . . . . . . . . . . . . . . . . . 7 66 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 67 5.1. New RTCP SDES Type value . . . . . . . . . . . . . . . . . 9 68 5.2. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9 69 5.3. Contact information for registrations . . . . . . . . . . 9 70 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 71 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 72 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 73 7.2. Informative References . . . . . . . . . . . . . . . . . . 11 74 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 12 75 A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-00 . . . . . . . 12 76 A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-01 . . . . . . . 12 77 A.3. draft-ietf-xrblock-xr-rtcp-meas-identity-02 . . . . . . . 12 78 A.4. draft-ietf-xrblock-xr-rtcp-meas-identity-03 . . . . . . . 13 79 A.5. draft-ietf-xrblock-xr-rtcp-meas-identity-04 . . . . . . . 13 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 82 1. Introduction 84 This draft defines one new RTCP SDES item and one new XR Report Block 85 carrying parameters that identify and describe a measurement period, 86 to which one or more other RTCP XR Report Blocks may refer. 88 The SDES item provides a field for an application specific auxiliary 89 identifier. This identifier may be used to correlate data in XR 90 Blocks within an RTP session with data from a non-RTP session. 92 A RTCP Measurement Identity SDES packet MAY be associated with a set 93 of RTCP XR metrics blocks which share the same application specific 94 measurement identifier. 96 The XR Report Block does not contain any measurement results 97 (metrics). Rather, it provide information relevant to a measurement 98 reported in one or more other block types, including: 100 o the sequence number of the first packet of the RTP session, 102 o the extended sequence numbers of the first packet of the current 103 measurement interval, and the last packet included in the 104 measurement, 106 o the duration of the most recent measurement interval and 108 o the duration of the interval applicable to cumulative measurements 109 (which may be the duration of the RTP session to date). 111 The method for calculation of the extended RTP sequence number is 112 provide in [RFC3550]. 114 The RTCP XR Report Block containing the measurement information is 115 intended to provide a single copy of the information necessary to 116 relate measurement data in the RTCP XR blocks to the stream, and 117 measurement period, to which they refer. Commonly, multiple other 118 small metric blocks contain measurement data for the same stream and 119 period, and it would be a large overhead if all of these metric 120 blocks carried duplicated data for measurement identification. 122 The RTCP XR Report Block MAY be associated with a set of RTCP XR 123 metrics blocks which share the same information relevant to a 124 reported measurement. There MAY be several such sets in an RTCP 125 packet, in which each set share the same information relevant to a 126 reported measurement. There MAY also be RTCP XR blocks in the packet 127 which are not associated with a Measurement Information block, for 128 example blocks which were defined before the Measurement Identity and 129 information mechanism was introduced by this document. 131 1.1. RTCP and RTCP XR Reports 133 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 134 defined an extensible structure for reporting using an RTCP Extended 135 Report (XR). This draft defines a new Extended Report block that 136 MUST be used as defined in [RFC3550] and [RFC3611]. 138 1.2. Performance Metrics Framework 140 The Performance Metrics Framework [RFC6390] provides guidance on the 141 definition and specification of performance metrics. The RTP 142 Monitoring Architectures[MONARCH] provides guideline for reporting 143 block format using RTCP XR . The SDES item and XR Block described in 144 this draft are in accordance with [RFC6390] and [MONARCH]. 146 1.3. Applicability 148 The RTCP SDES item and the RTCP XR block defined in this document 149 provides information relevant to the measurements for members of a 150 family of RTCP XR metrics blocks which are designed to use it. To 151 use the mechanism defined here, the RTCP XR block containing 152 measurement information is not required to be in the same RTCP packet 153 as the SDES item containing measurement identity. 155 2. Terminology 157 2.1. Standards Language 159 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 160 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 161 document are to be interpreted as described in RFC 2119 [RFC2119] 163 3. Measurement Identity SDES Item 165 This section defines the format of the Measurement Identity SDES 166 item. The SDES item is carried in the RTCP SDES packet. The packet 167 format for the RTCP SDES is defined in Section 6.5 of [RFC3550]. 168 Each SDES packet is composed of a header with fixed-length fields for 169 version, source count, packet type (PT), and length, followed by zero 170 of more SDES items. In the SDES packet, the PT field is set to SDES 171 (202). 173 3.1. APSI: Application Specific Identifier SDES Item 175 0 1 2 3 176 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 177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 178 | APSI=TBD | length |application specific identifier 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | .... 181 +-+-+-+-+-+-+-+-+ 183 Application specific identifier is an additional identifier which is 184 useful in the context of a specific application, e.g. an MPEG-2 185 transport identifier [MPEG2]. This item MUST be ignored by 186 applications that are not configured to make use of it. The 187 identifier is variable length. Its length is described by the length 188 field. The value of the length field does not include the two octet 189 SDES item header. If no identifier is provided, the length field 190 MUST be set to zero. 192 4. Measurement Information XR Block 194 4.1. Report Block Structure 196 0 1 2 3 197 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 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | BT=NMI | Reserved | block length = 6 | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 | SSRC of stream source | 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 203 | Reserved | first sequence number | 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | extended first sequence number of interval | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | extended last sequence number | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 | Measurement Duration (Cumulative) | 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 211 | Measurement Duration (Interval) | 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 Report Block Structure 216 4.2. Definition of Fields in Measurement Information Report Block 218 Block type (BT): 8 bits 220 A Measurement Information Report Block is identified by the 221 constant NMI. 223 [Note to RFC Editor: please replace NMI with the IANA provided 224 RTCP XR block type for this block.] 226 Reserved.: 8 bits 228 These bits are reserved. They MUST be set to zero by senders and 229 ignored by receivers. 231 Block Length: 16 bits 233 The length of this report block in 32-bit words minus one. For 234 the Measurement Information block, the block length is equal to 6. 236 SSRC of source: 32 bits 238 As defined in Section 4.1 of [RFC3611]. 240 Reserved: 16 bits 242 These bits are reserved. They MUST be set to zero by senders and 243 ignored by receivers. 245 First sequence number: 16 bits 247 The RTP sequence number of the first received RTP packet of the 248 session, used to determine the number of packets contributing to 249 cumulative measurements. 251 Extended first sequence number of interval: 32 bits 253 The extended RTP sequence number of the first received RTP packet 254 of the current measurement interval. 256 Extended last sequence number: 32 bits 258 The extended RTP sequence number of the last received RTP packet 259 which contributed to this measurement. 261 Measurement Duration (Cumulative) : 32 bits 263 The duration, expressed in units of 1/65536 seconds, of the 264 reporting interval applicable to Cumulative reports which use this 265 Measurement Information block. The value of this field can be 266 calculated by the receiver of the RTP media stream, for example, 267 based on received RTP media packets or using RTCP method described 268 in [RFC3550]. 270 Measurement Duration (Interval) : 32 bits 272 The duration, expressed in units of 1/65536 seconds, of the 273 reporting interval applicable to Interval reports which use this 274 Measurement Information block . The value of this field can be 275 calculated by the receiver of the RTP media stream, for example, 276 based on received RTP media packets or using RTCP method described 277 in [RFC3550]. 279 5. IANA Considerations 281 New SDES types for RTCP SDES are subject to IANA registration. For 282 general guidelines on IANA considerations for RTCP SDES, refer to 283 [RFC3550]. 285 5.1. New RTCP SDES Type value 287 This document assigns one additional SDES type in the IANA "RTCP XR 288 Block Type Registry" to the Measurement Identity SDES items as 289 follow: 291 abbrev. name value 292 APSI: Application Specific Identifier TBD 294 [Note to RFC Editor: please replace APSI with the IANA provided RTCP 295 SDES type for the SDES item.] 297 5.2. New RTCP XR Block Type value 299 This document assigns the block type value NMI in the IANA "RTCP XR 300 Block Type Registry" to the "Measurement Information Block". 302 [Note to RFC Editor: please replace NMI with the IANA provided RTCP 303 XR block type for this block.] 305 5.3. Contact information for registrations 307 The contact information for the registrations is: 309 Qin Wu (sunseawq@huawei.com) 311 101 Software Avenue, Yuhua District 312 Nanjing, Jiangsu 210012 313 China 315 6. Security Considerations 317 RTCP reports can contain sensitive information, including information 318 about the nature and duration of a session established between two or 319 more endpoints. Therefore, the use of security mechanisms with RTP, 320 as documented in Section 9 of [RFC3550] should apply. 322 7. References 324 7.1. Normative References 326 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 327 Requirement Levels", March 1997. 329 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 330 Applications", RFC 3550, July 2003. 332 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 333 Protocol Extended Reports (RTCP XR)", November 2003. 335 7.2. Informative References 337 [MONARCH] Wu, Q., Hunt, G., and P. , "Monitoring Architectures for 338 RTP", ID draft-ietf-avtcore-monarch-11, March 2012. 340 [MPEG2] "ISO/IEC, "Standard 13818-1"", December 2000. 342 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 343 Development", RFC 6390, October 2011. 345 Appendix A. Change Log 347 Note to the RFC-Editor: please remove this section prior to 348 publication as an RFC. 350 A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-00 352 The following are the major changes to 353 draft-ietf-avt-rtcp-xr-meas-identity-02: 355 o Change the use of SDES item to convey measurement identity instead 356 of XR Block in section 2. 358 o Update references. 360 o Update security section and remove SDP signaling section. 362 A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-01 364 The following are the major changes to 365 draft-ietf-xrblock-xr-rtcp-meas-identity-00: 367 o Replace SDES item containing additional measurement information 368 with XR Block. 370 o Add section 2 to describe following RFC2119 language. 372 o Add Section 1.2 to make SDES item and XR Report be compliant with 373 RFC3550 and RFC3611 375 o Add Section 1.3 to make SDES item and XR Report follow Performance 376 Metrics Framework and RTP Monitoring Architecture. 378 o Add section5.2 to register the new RTCP XR Block Type value. 380 o Remove RTCP SDES Type values that are needed. 382 A.3. draft-ietf-xrblock-xr-rtcp-meas-identity-02 384 The following are the major changes to 385 draft-ietf-xrblock-xr-rtcp-meas-identity-01: 387 o Relocating information that belong to SDES item and XR Block 388 respectively in the section 1. 390 o Rephrasing the text that describes SDES packet composition. 392 o Rephrasing identifier description. 394 o Other Editorial changes. 396 A.4. 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.5. draft-ietf-xrblock-xr-rtcp-meas-identity-04 405 The following are the major changes to 406 draft-ietf-xrblock-xr-rtcp-meas-identity-03: 408 o Change unit of measurement duration from ms to 1/65536 seconds. 410 Authors' Addresses 412 Geoff Hunt 413 Unaffiliated 415 Email: r.geoff.hunt@gmail.com 417 Alan Clark 418 Telchemy Incorporated 419 2905 Premiere Parkway, Suite 280 420 Duluth, GA 30097 421 USA 423 Email: alan.d.clark@telchemy.com 425 Qin Wu 426 Huawei 427 101 Software Avenue, Yuhua District 428 Nanjing, Jiangsu 210012 429 China 431 Email: sunseawq@huawei.com