]> Aalto University

School of Electrical Engineering Otakaari 5 A Espoo FIN02150 Finland jo@comnet.tkk.fi

Aalto University

School of Electrical Engineering Otakaari 5 A Espoo FIN 02150 Finland varun@comnet.tkk.fi http://www.netlab.tkk.fi/~varun/

Nokia Research Center

P.O. Box 1000 (Visiokatu 3) Tampere FIN33721 Finland igor.curcio@nokia.com

RAI XR Block Working Group RTP RTCP discard metrics The RTP Control Protocol (RTCP) is used in conjunction with the Real- time Transport Protocol (RTP) in order to provide a variety of short-term and long-term reception statistics. The available reporting may include aggregate information across longer periods of time as well as individual packet reporting. This document specifies a per-packet report metric capturing individual packets discarded from the de-jitter buffer after successful reception.

RTP provides a transport for real-time media flows such as audio and video together with the RTP Control Protocol (RTCP), which provides periodic feedback about the media streams received in a specific duration. In addition, RTCP can be used for timely feedback about individual events to report (e.g., packet loss) . Both long-term and short-term feedback enable a media sender to adapt its media transmission and/or encoding dynamically to the observed path characteristics. RFC 3611 defines RTCP Extended Reports as a detailed reporting framework to provide more than just the coarse Receiver Report (RR) statistics. The detailed reporting may enable a media sender to react more appropriately to the observed networking conditions as these can be characterized better, although at the expense of extra overhead. Among many other report blocks, RFC 3611 specifies the Loss Run Length Encoding (RLE) block, which reports runs of packets received and lost with the granularity of individual packets. This can help both error recovery and path loss characterization. In addition to lost packets, RFC 3611 defines the notion of "discarded" packets: packets that were received but dropped from the de-jitter buffer because they were either too early (for buffering) or too late (for playout). The "discard rate" metric is part of the Voice over IP (VoIP) metrics report block even though it is not just applicable to audio: it is specified as the fraction of discarded packets since the beginning of the session (see Section 4.7.1 of RFC 3611). The discard metric is believed to be applicable to a large class of RTP applications that use a de-jitter buffer . Recently proposed extensions to the Extended Reports (XRs) reporting suggest enhancing this discard metric: Reporting the number of discarded packets in a measurement interval, i.e., either during the last reporting interval or since the beginning of the session, as indicated by a flag in the suggested XR . If an endpoint needs to report packet discard due to reasons other than early and late arrival (for example, discard due to duplication, redundancy, etc.), then it should consider using the Discarded Packets report block . Reporting gaps and bursts of discarded packets during a measurement interval, i.e., the last reporting interval or the duration of the session . Reporting the sum of payload bytes discarded during a measurement interval, i.e., the last reporting interval or the duration of the session . However, none of these metrics allow a receiver to report precisely which packets were discarded. While this information could in theory be derived from high-frequency reporting on the number of discarded packets or from the gap/burst report , these two mechanisms do not appear feasible: the former would require an unduly high amount of reporting, which still might not be sufficient due to the non-deterministic scheduling of RTCP packets. The latter incurs significant complexity and reporting overhead and might still not deliver the desired accuracy. This document defines a discard report block following the idea of the run-length encoding applied for lost and received packets in .

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 . The terminology defined in RTP and in the extensions for XR reporting applies.

The RTCP XR Discard RLE report block uses the same format as specified for the loss and duplicate report blocks in RFC 3611. describes the packet format. The fields "BT", "T", "block length", "SSRC of source", "begin_seq", and "end_seq" have the same semantics and representation as defined in , with the addition of the "E" flag to indicate the reason for discard. The "chunks" encoding the run length have the same representation as in RFC 3611, but encode discarded packets. A definition of a discarded packet is given in RFC 7002.

Block Type (BT, 8 bits): A Discard RLE report block is identified by the constant 25. rsvd (3 bits): This field is reserved for future definition. In the absence of such definition, the bits in this field MUST be set to zero and MUST be ignored by the receiver. The 'E' bit is introduced to distinguish between packets discarded due to early arrival and those discarded due to late arrival. The 'E' bit is set to '1' if the chunks represent packets discarded due to arriving too early and is set to '0' otherwise. In case both early and late discarded packets shall be reported, two Discard RLE report blocks MUST be included; their sequence number range MAY overlap, but individual packets MUST only be reported as either early or late and not appear marked in both. If packets appear in both report blocks, the conflicting packets will be ignored. Packets not reported in either block are considered to be properly received and not discarded. Discard RLE report blocks SHOULD be sent in conjunction with an RTCP RR as a compound RTCP packet.

This section describes the behavior of the reporting node (= media receiver) and the media sender.

Transmission of RTCP XR Discard RLE report blocks is up to the discretion of the media receiver, as is the reporting granularity. However, it is RECOMMENDED that the media receiver signal all discarded packets using the method defined in this document. If all packets over a reporting period are discarded, the media receiver MAY use the Discard Report Block instead. In case of limited available reporting bandwidth, it is up to the receiver whether or not to include RTCP XR Discard RLE report blocks. The media receiver MAY send the Discard RLE report blocks as part of the regularly scheduled RTCP packets, as per RFC 3550. It MAY also include Discard RLE report blocks in immediate or early feedback packets, as per RFC 4585.

The media sender MUST be prepared to operate without receiving any Discard RLE report blocks. If Discard RLE report blocks are generated by the media receiver, the media sender cannot rely on all these reports being received, nor can the media sender rely on a regular generation pattern from the media receiver. However, if the media sender receives RTCP XR reports but the reports contain no Discard RLE report blocks and is aware that the media receiver supports Discard RLE report blocks, it MAY assume that no packets were discarded at the media receiver.

A participant of a media session MAY use SDP to signal its support for the report block specified in this document or use them without any prior signaling (see Section 5 of RFC 3611). For signaling in SDP, the RTCP XR attribute as defined in RFC 3611 MUST be used. The SDP attribute 'xr-format' defined in RFC 3611 is augmented as described in the following to indicate the discard RLE metric.

The parameter 'discard-rle' is used to indicate support for the Discard RLE report block defined in . When SDP is used in Offer/Answer context, the mechanism defined in RFC 3611 for unilateral "rtcp-xr" attribute parameters applies (see Section 5.2 of RFC 3611).

The Discard RLE report block provides per-packet statistics so the risk to confidentiality documented in Section 7, Paragraph 3, of RFC 3611 applies. In some situations, returning very detailed error information (e.g., over-range measurement or measurement unavailable) using this report block can provide an attacker with insight into the security processing. Implementers should consider the guidance in for using appropriate security mechanisms, i.e., where security is a concern, the implementation should apply encryption and authentication to the report block. For example, this can be achieved by using the AVPF profile together with the Secure RTP profile as defined in RFC 3711; an appropriate combination of the two profiles (an "SAVPF") is specified in RFC 5124. However, other mechanisms also exist and might be more suitable. Additionally, The security considerations of RFC 3550, RFC 3611, and RFC 4585 apply.

New block types for RTCP XR are subject to IANA registration. For general guidelines on IANA considerations for RTCP XR, refer to RFC 3611.

This document extends the IANA "RTP Control Protocol Extended Reports (RTCP XR) Block Type Registry" by assigning value 25 to DRLE (Discard RLE Report).

This document registers 'discard-rle' in the "RTCP XR SDP Parameters".

Joerg Ott (jo@comnet.tkk.fi) Aalto University Comnet, Otakaari 5A, 02150 Espoo, Finland.

The authors would like to thank Alan Clark, Roni Even, Sam Hartman, Colin Perkins, Dan Romascanu, Dan Wing, and Qin Wu for providing valuable feedback on earlier draft versions of this document.

&rfc2119; &rfc3550; &rfc3611; &rfc4585; &rfc4566; &rfc7002; &rfc7003; &rfc5481; &rfc3711; &rfc5124; This memo discusses the problem of securing real-time multimedia sessions, and explains why the Real-time Transport Protocol (RTP), and the associated RTP Control Protocol (RTCP), do not mandate a single media security mechanism. Guidelines for designers and reviewers of future RTP extensions are provided, to ensure that appropriate security mechanisms are mandated, and that any such mechanisms are specified in a manner that conforms with the RTP architecture. The Real-time Transport Protocol (RTP) is used in a large number of different application domains and environments. This heterogeneity implies that different security mechanisms are needed to provide services such as confidentiality, integrity and source authentication of RTP/RTCP packets suitable for the various environments. The range of solutions makes it difficult for RTP-based application developers to pick the most suitable mechanism. This document provides an overview of a number of security solutions for RTP, and gives guidance for developers on how to choose the appropriate security mechanism. The RTP Control Protocol (RTCP) is used in conjunction with the Real- time Transport Protocol (RTP) in to provide a variety of short-term and long-term reception statistics. The available reporting may include aggregate information across longer periods of time as well as individual packet reporting. This document specifies a report computing the bytes discarded from the de-jitter buffer after successful reception.

RLE of Discarded RTP Packets Metric Metric Name: RLE - Run-length encoding of Discarded RTP Packets Metric. Metric Description: Instances of RTP packets discarded over the period covered by this report. Method of Measurement or Calculation: See , for the definition of Discard RLE [RFC7097] and Section 4.1 of RFC 3611 for RLE. Units of Measurement: Every RTP packet in the interval is reported as discarded or not. See of RFC 7097 [RFC7097] for the definition. Measurement Point(s) with Potential Measurement Domain: The measurement of these metrics is made at the receiving end of the RTP stream. Measurement Timing: Each RTP packet between a beginning sequence number (begin_seq) and ending sequence number (end_seq) is reported as discarded or not. See of RFC 7097 [RFC7097] for the definition of Discard RLE. Use and applications: See , Paragraph 1, of [RFC7097]. Reporting model: See RFC 3611.