idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-meas-identity-01.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 (October 13, 2011) is 4580 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-04 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: April 15, 2012 Telchemy 6 Q. Wu 7 Huawei 8 October 13, 2011 10 Measurement Identity and information Reporting using SDES item and XR 11 Block 12 draft-ietf-xrblock-rtcp-xr-meas-identity-01.txt 14 Abstract 16 This document defines a RTCP SDES item and a RTCP XR Block carrying 17 parameters which identify a measurement, to which one or more other 18 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 April 15, 2012. 37 Copyright Notice 39 Copyright (c) 2011 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 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 79 1. Introduction 81 This draft defines one new RTCP SDES item and one new XR Report Block 82 to carry parameters which identify a measurement for use in a range 83 of RTP applications. The SDES item and the XR Report Block do not 84 itself contain any measurement results (metrics).However, they 85 provide information relevant to a measurement reported in one or more 86 other block types, including 88 o a field for incorporation of an application-specific auxiliary 89 identifier, 91 o the sequence number of the first packet of the RTP session, 93 o the extended sequence numbers of the first packet of the current 94 measurement interval, and the last packet included in the 95 measurement, 97 o the duration of the most recent measurement interval and 99 o the duration of the interval applicable to cumulative measurements 100 (which may be the duration of the RTP session to date). 102 The method for calculation of the extended RTP sequence number is 103 provide in [RFC3550]. 105 The RTCP SDES item containing the measurement identity is intended to 106 provide information to relate RTP to a non-RTP session while the RTCP 107 XR Report Block containing the measurement information is intended to 108 provide a single copy of the information necessary to relate 109 measurement data in the RTCP XR blocks to the stream, and measurement 110 period, to which they refer. Commonly, multiple other small metric 111 blocks contain measurement data for the same stream and period, and 112 it would be a large overhead if all of these metric blocks carried 113 duplicated data for measurement identification. 115 A RTCP Measurement Identity SDES packet MAY be associated with a set 116 of RTCP XR metrics blocks which share the same application specific 117 measurement identifier. 119 The RTCP XR Report Block MAY be associated with a set of RTCP XR 120 metrics blocks which share the same information relevant to a 121 reported measurement. There MAY be several such sets in an RTCP 122 packet, in which each set share the same information relevant to a 123 reported measurement. There MAY also be RTCP XR blocks in the packet 124 which are not associated with a Measurement Information block, for 125 example blocks which were defined before the Measurement Identity and 126 information mechanism was introduced by this document. 128 1.1. RTCP and RTCP XR Reports 130 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 131 defined an extensible structure for reporting using an RTCP Extended 132 Report (XR). This draft defines a new Extended Report block that 133 MUST be used as defined in [RFC3550] and [RFC3611]. 135 1.2. Performance Metrics Framework 137 The Performance Metrics Framework [PMOLFRAME] provides guidance on 138 the definition and specification of performance metrics. The RTP 139 Monitoring Architectures[MONARCH] provides guideline for reporting 140 block format using RTCP XR . Metrics or SDES item described in this 141 draft either reference external definitions or define metrics 142 generally in accordance with [PMOLFRAME][MONARCH]. 144 1.3. Applicability 146 The RTCP SDES item and the RTCP XR block defined in this document 147 provides information relevant to the measurement for members of a 148 family of RTCP XR metrics blocks which are designed to use it. To 149 use the mechanism defined here, the RTCP XR block containing 150 measurement information is not required in the same RTCP packet as 151 the SDES item contain measurement identity. 153 2. Terminology 155 2.1. Standards Language 157 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 158 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 159 document are to be interpreted as described in RFC 2119 [RFC2119] 161 3. Measurement Identity SDES Item 163 This section defines the format of Measurement Identity SDES item. 164 The SDES item is carried in the RTCP SDES packet. The packet format 165 for the RTCP SDES is defined in Section 6.5 of [RFC3550]. Each SDES 166 packet has a fixed-length field for version, source count, packet 167 type (PT), length as well as a variable-length field for the SDES 168 item. In the SDES packet, the PT field is set to SDES (202). 170 3.1. APSI: Application Specific Identifier SDES Item 172 0 1 2 3 173 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 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 | APSI=TBD | length |application specific identifier 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 | .... 178 +-+-+-+-+-+-+-+-+ 180 Application specific identifier is an additional identifier which is 181 useful in the context of a specific application, e.g. an MPEG-2 182 transport identifier [MPEG2]. Where the identifier is less than 32 183 bits, the identifier SHOULD be mapped into the most significant bits 184 of the field. If no additional identifier is provided, all bits of 185 the field MUST be set to zero. This item MUST be ignored by 186 applications which are not configured to make use of it. 188 4. Measurement Information XR Block 190 4.1. Report Block Structure 192 0 1 2 3 193 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 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | BT=NMI | Rsv. | block length = 6 | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | SSRC of stream source | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | reserved | first seq num | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 | extended first sequence number of interval | 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 203 | extended last sequence number | 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | Measurement Duration (Cumulative) (ms) | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | Measurement Duration (Interval) (ms) | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 210 Report Block Structure 212 4.2. Definition of Fields in Measurement Information Report Block 214 Block type (BT): 8 bits 216 A Measurement Information Report Block is identified by the 217 constant NMI. 219 [Note to RFC Editor: please replace NMI with the IANA provided 220 RTCP XR block type for this block.] 222 Rsv.: 8 bits 224 This field is reserved for future definition. In the absence of 225 such a definition, the bits in this field MUST be set to zero and 226 MUST be ignored by the receiver. 228 Block Length: 16 bits 230 The length of this report block in 32-bit words minus one. For 231 the Measurement Information block, the block length is equal to 7. 233 SSRC of source: 32 bits 235 As defined in Section 4.1 of [RFC3611]. 237 Reserved: 16 bits 239 These bits are reserved. They MUST be ignored by receivers. They 240 MUST be set to zero by senders. 242 First seq num: 16 bits 244 The RTP sequence number of the first received RTP packet of the 245 session, used to determine the number of packets contributing to 246 cumulative measurements. 248 Extended first sequence number of interval: 32 bits 250 The extended RTP sequence number of the first received RTP packet 251 of the current measurement interval. 253 Extended last sequence number: 32 bits 255 The extended RTP sequence number of the last received RTP packet 256 which contributed to this measurement. 258 Measurement Duration (Cumulative) (ms): 32 bits 260 The duration in ms of the reporting interval applicable to 261 Cumulative reports which use this Measurement Information block. 263 Measurement Duration (Interval) (ms): 32 bits 265 The duration in ms of the reporting interval applicable to 266 Interval reports which use this Measurement Information block. 268 5. IANA Considerations 270 New SDES types for RTCP SDES are subject to IANA registration. For 271 general guidelines on IANA considerations for RTCP SDES, refer to 272 [RFC3550]. 274 5.1. New RTCP SDES Type value 276 This document assigns additional five SDES types in the IANA "RTCP XR 277 Block Type Registry" to the Measurement Identity SDES items as 278 follow: 280 abbrev. name value 281 APSI: Application Specific Identifier TBD 283 [Note to RFC Editor: please replace APSI with the IANA provided RTCP 284 SDES type for the SDES item.] 286 5.2. New RTCP XR Block Type value 288 This document assigns the block type value NMI in the IANA "RTCP XR 289 Block Type Registry" to the "Measurement Information Block". 291 [Note to RFC Editor: please replace NMI with the IANA provided RTCP 292 XR block type for this block.] 294 5.3. Contact information for registrations 296 The contact information for the registrations is: 298 Qin Wu (sunseawq@huawei.com) 300 101 Software Avenue, Yuhua District 301 Nanjing, Jiangsu 210012 302 China 304 6. Security Considerations 306 RTCP reports can contain sensitive information since they can provide 307 information about the nature and duration of a session established 308 between two or more endpoints.Therefore, the use of security 309 mechanisms with RTP documented in Section 9 of [RFC3550] should 310 apply. 312 7. References 314 7.1. Normative References 316 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 317 Requirement Levels", March 1997. 319 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 320 Applications", RFC 3550, July 2003. 322 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 323 Protocol Extended Reports (RTCP XR)", November 2003. 325 7.2. Informative References 327 [MONARCH] Wu, Q., "Monitoring Architectures for RTP", 328 ID draft-ietf-avtcore-monarch-04, August 2011. 330 [MPEG2] "ISO/IEC, "Standard 13818-1"", December 2000. 332 [PMOLFRAME] 333 Clark, A. and B. Claise, "Framework for Performance Metric 334 Development", ID draft-ietf-pmol-metrics-framework-12, 335 July 2011. 337 Appendix A. Change Log 339 Note to the RFC-Editor: please remove this section prior to 340 publication as an RFC. 342 A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-00 344 The following are the major changes to 345 draft-ietf-avt-rtcp-xr-meas-identity-02: 347 o Change the use of SDES item to convey measurement identity instead 348 of XR Block in section 2. 350 o Update references. 352 o Update security section and remove SDP signaling section. 354 A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-01 356 The following are the major changes to 357 draft-ietf-xrblock-xr-rtcp-meas-identity-00: 359 o Replace SDES item containing additional measurement information 360 with XR Block. 362 o Add section 2 to describe following RFC2119 language. 364 o Add Section 1.2 to make SDES item and XR Report be compliant with 365 RFC3550 and RFC3611 367 o Add Section 1.3 to make SDES item and XR Report follow Performance 368 Metrics Framework and RTP Monitoring Architecture. 370 o Add section5.2 to register the new RTCP XR Block Type value. 372 o Remove RTCP SDES Type values that are needed. 374 Authors' Addresses 376 Geoff Hunt 377 Unaffiliated 379 Email: r.geoff.hunt@gmail.com 381 Alan Clark 382 Telchemy Incorporated 383 2905 Premiere Parkway, Suite 280 384 Duluth, GA 30097 385 USA 387 Email: alan.d.clark@telchemy.com 389 Qin Wu 390 Huawei 391 101 Software Avenue, Yuhua District 392 Nanjing, Jiangsu 210012 393 China 395 Email: sunseawq@huawei.com