draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02.txt   draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-03.txt 
XR Block Working Group J. Ott XR Block Working Group J. Ott
Internet-Draft V. Singh Internet-Draft V. Singh
Intended status: Standards Track Aalto University Intended status: Standards Track Aalto University
Expires: August 2, 2012 I. Curcio Expires: August 5, 2012 I. Curcio
Nokia Research Center Nokia Research Center
January 30, 2012 February 2, 2012
Real-time Transport Control Protocol (RTCP) Extension Report (XR) for Real-time Transport Control Protocol (RTCP) Extension Report (XR) for
Run Length Encoding of Discarded Packets Run Length Encoding of Discarded Packets
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02.txt draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-03.txt
Abstract Abstract
The Real-time Transport Control Protocol (RTCP) is used in The Real-time Transport Control Protocol (RTCP) is used in
conjunction with the Real-time Transport Protocol (RTP) in to provide conjunction with the Real-time Transport Protocol (RTP) in to provide
a variety of short-term and long-term reception statistics. The a variety of short-term and long-term reception statistics. The
available reporting may include aggregate information across longer available reporting may include aggregate information across longer
periods of time as well as individual packet reporting. This periods of time as well as individual packet reporting. This
document specifies a per-packet report metric capturing individual document specifies a per-packet report metric capturing individual
packets discarded from the jitter buffer after successful reception. packets discarded from the jitter buffer after successful reception.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 2, 2012. This Internet-Draft will expire on August 5, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 16 skipping to change at page 2, line 16
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. XR Discard RLE Report Block . . . . . . . . . . . . . . . . . 4 3. XR Discard RLE Report Block . . . . . . . . . . . . . . . . . 4
4. XR Bytes Discarded Report Block . . . . . . . . . . . . . . . 5 4. XR Bytes Discarded Report Block . . . . . . . . . . . . . . . 5
5. Protocol Operation . . . . . . . . . . . . . . . . . . . . . . 6 5. Protocol Operation . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Reporting Node (Receiver) . . . . . . . . . . . . . . . . 6 5.1. Reporting Node (Receiver) . . . . . . . . . . . . . . . . 7
5.2. Media Sender . . . . . . . . . . . . . . . . . . . . . . . 7 5.2. Media Sender . . . . . . . . . . . . . . . . . . . . . . . 7
6. SDP signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 6. SDP signaling . . . . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8.1. XR Report Block Registration . . . . . . . . . . . . . . . 8 8.1. XR Report Block Registration . . . . . . . . . . . . . . . 9
8.2. SDP Parameter Registration . . . . . . . . . . . . . . . . 8 8.2. SDP Parameter Registration . . . . . . . . . . . . . . . . 9
8.3. Contact information for IANA registrations . . . . . . . . 8 8.3. Contact information for IANA registrations . . . . . . . . 9
9. Normative References . . . . . . . . . . . . . . . . . . . . . 9 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
10. Normative References . . . . . . . . . . . . . . . . . . . . . 9
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 10 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 10
A.1. changes in A.1. changes in
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-00 . . . . 10 draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-00 . . . . 10
A.2. changes in A.2. changes in
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01 . . . . 10 draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01 . . . . 11
A.3. changes in A.3. changes in
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02 . . . . 10 draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02 . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 A.4. changes in
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-03 . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
RTP [RFC3550] provides a transport for real-time media flows such as RTP [RFC3550] provides a transport for real-time media flows such as
audio and video together with the RTP control protocol which provides audio and video together with the RTP control protocol which provides
periodic feedback about the media streams received in a specific periodic feedback about the media streams received in a specific
duration. In addition, RTCP can be used for timely feedback about duration. In addition, RTCP can be used for timely feedback about
individual events to report (e.g., packet loss) [RFC4585]. Both individual events to report (e.g., packet loss) [RFC4585]. Both
long-term and short-term feedback enable a sender to adapt its media long-term and short-term feedback enable a sender to adapt its media
transmission and/or encoding dynamically to the observed path transmission and/or encoding dynamically to the observed path
skipping to change at page 4, line 9 skipping to change at page 4, line 9
appear feasible: The former would require an unduly high amount of appear feasible: The former would require an unduly high amount of
reporting which still might not be sufficient due to the non- reporting which still might not be sufficient due to the non-
deterministic scheduling of RTCP packets. The latter incur deterministic scheduling of RTCP packets. The latter incur
significant complexity and reporting overhead and might still not significant complexity and reporting overhead and might still not
deliver the desired accuracy. deliver the desired accuracy.
This document defines a discard report block following the idea of This document defines a discard report block following the idea of
the run-length encoding applied for lost and received packets in the run-length encoding applied for lost and received packets in
RFC3611 [RFC3611]. RFC3611 [RFC3611].
Complementary to or instead of the indication which packets were
discarded, an XR block is defined to indicate the number of bytes
discarded, per interval or for the duration of the session, similar
to other XR report blocks.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119] and indicate requirement levels for compliant [RFC2119] and indicate requirement levels for compliant
implementations. implementations.
The terminology defined in RTP [RFC3550] and in the extensions for XR The terminology defined in RTP [RFC3550] and in the extensions for XR
reporting [RFC3611] applies. reporting [RFC3611] applies.
3. XR Discard RLE Report Block 3. XR Discard RLE Report Block
The XR Discard RLE report block uses the same format as specified for The XR Discard RLE report block uses the same format as specified for
the loss and duplicate report blocks in RFC3611 [RFC3611]. Figure the loss and duplicate report blocks in RFC3611 [RFC3611]. Figure
Figure 1 recaps the packet format. The fields "BT", "T", "block Figure 1 recaps the packet format. The fields "BT", "T", "block
length", "SSRC of source", "begin_seq", and "end_seq" SHALL have the length", "SSRC of source", "begin_seq", and "end_seq" SHALL have the
same semantics and representation as defined in RFC3611. The same semantics and representation as defined in RFC3611 [RFC3611].
"chunks" encoding the run length SHALL have the same representation The "chunks" encoding the run length SHALL have the same
as in RFC3611, but encode discarded packets. representation as in RFC3611, but encode discarded packets.
0 1 2 3 0 1 2 3
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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=DRLE |rsvd |E| T | block length | | BT=DRLE |rsvd |E| T | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq | | begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 9 skipping to change at page 6, line 35
The 'E' bit is introduced to distinguish between packets discarded The 'E' bit is introduced to distinguish between packets discarded
due to early arrival and those discarded due to late arrival. The due to early arrival and those discarded due to late arrival. The
'E' bit MUST be set to '1' if the chunks represent packets discarded 'E' bit MUST be set to '1' if the chunks represent packets discarded
due to too early arrival and MUST be set to '0' otherwise. In case due to too early arrival and MUST be set to '0' otherwise. In case
both early and late discarded packets shall be reported, two Bytes both early and late discarded packets shall be reported, two Bytes
Discarded report blocks MUST be included. Discarded report blocks MUST be included.
These reserved bits (5 bits) SHOULD be set to zero by receivers and These reserved bits (5 bits) SHOULD be set to zero by receivers and
MUST be ignored by senders. MUST be ignored by senders.
block length (16 bits) MUST be set to 2, in accordance with the
definition of this field in RFC3611 [RFC3611]. The block MUST be
discarded if the block length is set to a different value.
The 'number of bytes discarded' is a 32-bit unsigned integer value The 'number of bytes discarded' is a 32-bit unsigned integer value
indicating the total number of bytes discarded. indicating the total number of bytes discarded.
If the XR block is not preceded by a measurement identity block If the XR block is not preceded by a measurement identity block
[I-D.ietf-xrblock-rtcp-xr-meas-identity] then the value indicates the [I-D.ietf-xrblock-rtcp-xr-meas-identity] then the value indicates the
bytes lost from from the start of the session (I=11), or the number bytes lost from from the start of the session (I=11), or the number
of bytes discarded since the last RTCP XR Bytes Discarded block was of bytes discarded since the last RTCP XR Bytes Discarded block was
received (I=10). received (I=10).
If the XR block follows a measurement identity block If the XR block follows a measurement identity block
skipping to change at page 9, line 5 skipping to change at page 9, line 32
This document registers two new parameters for the Session This document registers two new parameters for the Session
Description Protocol (SDP), "discard-rle" and "discard-bytes", in the Description Protocol (SDP), "discard-rle" and "discard-bytes", in the
"RTCP XR SDP Parameters Registry". "RTCP XR SDP Parameters Registry".
8.3. Contact information for IANA registrations 8.3. Contact information for IANA registrations
Joerg Ott (jo@comnet.tkk.fi) Joerg Ott (jo@comnet.tkk.fi)
Aalto University Comnet, Otakaari 5A, 02150 Espoo, Finland. Aalto University Comnet, Otakaari 5A, 02150 Espoo, Finland.
9. Normative References 9. Acknowledgements
Thanks to Qin Wu and Roni Even for providing valuable feedback on
earlier versions of this draft
10. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003. Applications", STD 64, RFC 3550, July 2003.
[RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and [RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and
Video Conferences with Minimal Control", STD 65, RFC 3551, Video Conferences with Minimal Control", STD 65, RFC 3551,
skipping to change at page 10, line 29 skipping to change at page 11, line 17
A.2. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01 A.2. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01
o Removed the measurement identification tag in the bytes discarded o Removed the measurement identification tag in the bytes discarded
block. block.
A.3. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02 A.3. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
o Removed the extra Tag bits from the Discarded bytes XR block. o Removed the extra Tag bits from the Discarded bytes XR block.
o Clarified use of measurement identity block in Section 4 and 5.2 o Clarified use of measurement identity block in Section 4 and 5.2
A.4. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-03
o Added explanation for block length in bytes discarded block
o Added an acknowledgement section
Authors' Addresses Authors' Addresses
Joerg Ott Joerg Ott
Aalto University Aalto University
Otakaari 5 A Otakaari 5 A
Espoo, FIN 02150 Espoo, FIN 02150
Finland Finland
Email: jo@comnet.tkk.fi Email: jo@comnet.tkk.fi
 End of changes. 14 change blocks. 
19 lines changed or deleted 41 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/