idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-meas-identity-03.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 (March 29, 2012) is 4404 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: September 30, 2012 Telchemy 6 Q. Wu 7 Huawei 8 March 29, 2012 10 Measurement Identity and information Reporting using SDES item and XR 11 Block 12 draft-ietf-xrblock-rtcp-xr-meas-identity-03.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 September 30, 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 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 81 1. Introduction 83 This draft defines one new RTCP SDES item and one new XR Report Block 84 carrying parameters that identify and describe a measurement period, 85 to which one or more other RTCP XR Report Blocks may refer. 87 The SDES item provides a field for an application specific auxiliary 88 identifier. This identifier may be used to correlate data in XR 89 Blocks within an RTP session with data from a non-RTP session. 91 A RTCP Measurement Identity SDES packet MAY be associated with a set 92 of RTCP XR metrics blocks which share the same application specific 93 measurement identifier. 95 The XR Report Block does not contain any measurement results 96 (metrics). Rather, it provide information relevant to a measurement 97 reported in one or more other block types, including: 99 o the sequence number of the first packet of the RTP session, 101 o the extended sequence numbers of the first packet of the current 102 measurement interval, and the last packet included in the 103 measurement, 105 o the duration of the most recent measurement interval and 107 o the duration of the interval applicable to cumulative measurements 108 (which may be the duration of the RTP session to date). 110 The method for calculation of the extended RTP sequence number is 111 provide in [RFC3550]. 113 The RTCP XR Report Block containing the measurement information is 114 intended to provide a single copy of the information necessary to 115 relate measurement data in the RTCP XR blocks to the stream, and 116 measurement period, to which they refer. Commonly, multiple other 117 small metric blocks contain measurement data for the same stream and 118 period, and it would be a large overhead if all of these metric 119 blocks carried duplicated data for measurement identification. 121 The RTCP XR Report Block MAY be associated with a set of RTCP XR 122 metrics blocks which share the same information relevant to a 123 reported measurement. There MAY be several such sets in an RTCP 124 packet, in which each set share the same information relevant to a 125 reported measurement. There MAY also be RTCP XR blocks in the packet 126 which are not associated with a Measurement Information block, for 127 example blocks which were defined before the Measurement Identity and 128 information mechanism was introduced by this document. 130 1.1. RTCP and RTCP XR Reports 132 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 133 defined an extensible structure for reporting using an RTCP Extended 134 Report (XR). This draft defines a new Extended Report block that 135 MUST be used as defined in [RFC3550] and [RFC3611]. 137 1.2. Performance Metrics Framework 139 The Performance Metrics Framework [RFC6390] provides guidance on the 140 definition and specification of performance metrics. The RTP 141 Monitoring Architectures[MONARCH] provides guideline for reporting 142 block format using RTCP XR . The SDES item and XR Block described in 143 this draft are in accordance with [RFC6390] and [MONARCH]. 145 1.3. Applicability 147 The RTCP SDES item and the RTCP XR block defined in this document 148 provides information relevant to the measurements for members of a 149 family of RTCP XR metrics blocks which are designed to use it. To 150 use the mechanism defined here, the RTCP XR block containing 151 measurement information is not required to be in the same RTCP packet 152 as the SDES item containing measurement identity. 154 2. Terminology 156 2.1. Standards Language 158 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 159 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 160 document are to be interpreted as described in RFC 2119 [RFC2119] 162 3. Measurement Identity SDES Item 164 This section defines the format of the Measurement Identity SDES 165 item. The SDES item is carried in the RTCP SDES packet. The packet 166 format for the RTCP SDES is defined in Section 6.5 of [RFC3550]. 167 Each SDES packet is composed of a header with fixed-length fields for 168 version, source count, packet type (PT), and length, followed by zero 169 of more SDES items. In the SDES packet, the PT field is set to SDES 170 (202). 172 3.1. APSI: Application Specific Identifier SDES Item 174 0 1 2 3 175 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 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 | APSI=TBD | length |application specific identifier 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 | .... 180 +-+-+-+-+-+-+-+-+ 182 Application specific identifier is an additional identifier which is 183 useful in the context of a specific application, e.g. an MPEG-2 184 transport identifier [MPEG2]. This item MUST be ignored by 185 applications that are not configured to make use of it. The 186 identifier is variable length. Its length is described by the length 187 field. The value of the length field does not include the two octet 188 SDES item header. If no identifier is provided, the length field 189 MUST be set to zero. 191 4. Measurement Information XR Block 193 4.1. Report Block Structure 195 0 1 2 3 196 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 197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 198 | BT=NMI | Reserved | block length = 6 | 199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 | SSRC of stream source | 201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 | Reserved | first sequence number | 203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 | extended first sequence number of interval | 205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 206 | extended last sequence number | 207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 208 | Measurement Duration (Cumulative) (ms) | 209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 210 | Measurement Duration (Interval) (ms) | 211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 Report Block Structure 215 4.2. Definition of Fields in Measurement Information Report Block 217 Block type (BT): 8 bits 219 A Measurement Information Report Block is identified by the 220 constant NMI. 222 [Note to RFC Editor: please replace NMI with the IANA provided 223 RTCP XR block type for this block.] 225 Reserved.: 8 bits 227 These bits are reserved. They MUST be set to zero by senders and 228 ignored by receivers. 230 Block Length: 16 bits 232 The length of this report block in 32-bit words minus one. For 233 the Measurement Information block, the block length is equal to 6. 235 SSRC of source: 32 bits 237 As defined in Section 4.1 of [RFC3611]. 239 Reserved: 16 bits 241 These bits are reserved. They MUST be set to zero by senders and 242 ignored by receivers. 244 First sequence number: 16 bits 246 The RTP sequence number of the first received RTP packet of the 247 session, used to determine the number of packets contributing to 248 cumulative measurements. 250 Extended first sequence number of interval: 32 bits 252 The extended RTP sequence number of the first received RTP packet 253 of the current measurement interval. 255 Extended last sequence number: 32 bits 257 The extended RTP sequence number of the last received RTP packet 258 which contributed to this measurement. 260 Measurement Duration (Cumulative) (ms): 32 bits 262 The duration in ms of the reporting interval applicable to 263 Cumulative reports which use this Measurement Information block. 264 The value of this field can be calculated by the receiver of the 265 RTP media stream, for example, based on received RTP media packets 266 or using RTCP method described in [RFC3550]. 268 Measurement Duration (Interval) (ms): 32 bits 270 The duration in ms of the reporting interval applicable to 271 Interval reports which use this Measurement Information block. 272 The value of this field can be calculated by the receiver of the 273 RTP media stream, for example, based on received RTP media packets 274 or using RTCP method described in [RFC3550]. 276 5. IANA Considerations 278 New SDES types for RTCP SDES are subject to IANA registration. For 279 general guidelines on IANA considerations for RTCP SDES, refer to 280 [RFC3550]. 282 5.1. New RTCP SDES Type value 284 This document assigns one additional SDES type in the IANA "RTCP XR 285 Block Type Registry" to the Measurement Identity SDES items as 286 follow: 288 abbrev. name value 289 APSI: Application Specific Identifier TBD 291 [Note to RFC Editor: please replace APSI with the IANA provided RTCP 292 SDES type for the SDES item.] 294 5.2. New RTCP XR Block Type value 296 This document assigns the block type value NMI in the IANA "RTCP XR 297 Block Type Registry" to the "Measurement Information Block". 299 [Note to RFC Editor: please replace NMI with the IANA provided RTCP 300 XR block type for this block.] 302 5.3. Contact information for registrations 304 The contact information for the registrations is: 306 Qin Wu (sunseawq@huawei.com) 308 101 Software Avenue, Yuhua District 309 Nanjing, Jiangsu 210012 310 China 312 6. Security Considerations 314 RTCP reports can contain sensitive information, including information 315 about the nature and duration of a session established between two or 316 more endpoints. Therefore, the use of security mechanisms with RTP, 317 as documented in Section 9 of [RFC3550] should apply. 319 7. References 321 7.1. Normative References 323 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 324 Requirement Levels", March 1997. 326 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 327 Applications", RFC 3550, July 2003. 329 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 330 Protocol Extended Reports (RTCP XR)", November 2003. 332 7.2. Informative References 334 [MONARCH] Wu, Q., Hunt, G., and P. , "Monitoring Architectures for 335 RTP", ID draft-ietf-avtcore-monarch-11, March 2012. 337 [MPEG2] "ISO/IEC, "Standard 13818-1"", December 2000. 339 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 340 Development", RFC 6390, October 2011. 342 Appendix A. Change Log 344 Note to the RFC-Editor: please remove this section prior to 345 publication as an RFC. 347 A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-00 349 The following are the major changes to 350 draft-ietf-avt-rtcp-xr-meas-identity-02: 352 o Change the use of SDES item to convey measurement identity instead 353 of XR Block in section 2. 355 o Update references. 357 o Update security section and remove SDP signaling section. 359 A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-01 361 The following are the major changes to 362 draft-ietf-xrblock-xr-rtcp-meas-identity-00: 364 o Replace SDES item containing additional measurement information 365 with XR Block. 367 o Add section 2 to describe following RFC2119 language. 369 o Add Section 1.2 to make SDES item and XR Report be compliant with 370 RFC3550 and RFC3611 372 o Add Section 1.3 to make SDES item and XR Report follow Performance 373 Metrics Framework and RTP Monitoring Architecture. 375 o Add section5.2 to register the new RTCP XR Block Type value. 377 o Remove RTCP SDES Type values that are needed. 379 A.3. draft-ietf-xrblock-xr-rtcp-meas-identity-02 381 The following are the major changes to 382 draft-ietf-xrblock-xr-rtcp-meas-identity-01: 384 o Relocating information that belong to SDES item and XR Block 385 respectively in the section 1. 387 o Rephrasing the text that describes SDES packet composition. 389 o Rephrasing identifier description. 391 o Other Editorial changes. 393 A.4. draft-ietf-xrblock-xr-rtcp-meas-identity-03 395 The following are the major changes to 396 draft-ietf-xrblock-xr-rtcp-meas-identity-02: 398 o The Editorial changes. 400 Authors' Addresses 402 Geoff Hunt 403 Unaffiliated 405 Email: r.geoff.hunt@gmail.com 407 Alan Clark 408 Telchemy Incorporated 409 2905 Premiere Parkway, Suite 280 410 Duluth, GA 30097 411 USA 413 Email: alan.d.clark@telchemy.com 415 Qin Wu 416 Huawei 417 101 Software Avenue, Yuhua District 418 Nanjing, Jiangsu 210012 419 China 421 Email: sunseawq@huawei.com