draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-00.txt   draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01.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: May 23, 2012 I. Curcio Expires: June 11, 2012 I. Curcio
Nokia Research Center Nokia Research Center
November 20, 2011 December 9, 2011
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-00.txt draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01.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 May 23, 2012. This Internet-Draft will expire on June 11, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 . . . . . . . . . . . . . . . . . . . . . . 7 5. Protocol Operation . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Reporting Node (Receiver) . . . . . . . . . . . . . . . . 7 5.1. Reporting Node (Receiver) . . . . . . . . . . . . . . . . 6
5.2. Media Sender . . . . . . . . . . . . . . . . . . . . . . . 7 5.2. Media Sender . . . . . . . . . . . . . . . . . . . . . . . 7
6. SDP signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 6. SDP signaling . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8.1. XR Report Block Registration . . . . . . . . . . . . . . . 8 8.1. XR Report Block Registration . . . . . . . . . . . . . . . 8
8.2. SDP Parameter Registration . . . . . . . . . . . . . . . . 9 8.2. SDP Parameter Registration . . . . . . . . . . . . . . . . 8
8.3. Contact information for IANA registrations . . . . . . . . 9 8.3. Contact information for IANA registrations . . . . . . . . 9
9. Normative References . . . . . . . . . . . . . . . . . . . . . 9 9. 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
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01 . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
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
skipping to change at page 5, line 38 skipping to change at page 5, line 38
In case both early and late discarded packets shall be reported, two In case both early and late discarded packets shall be reported, two
Discard RLE report blocks MUST be included; their sequence number Discard RLE report blocks MUST be included; their sequence number
range MAY overlap, but individual packets MUST only be reported as range MAY overlap, but individual packets MUST only be reported as
either early or late. Packets reported in both MUST be considered as either early or late. Packets reported in both MUST be considered as
discarded without further information available, packets reported in discarded without further information available, packets reported in
neither are considered to be properly received and not discarded. neither are considered to be properly received and not discarded.
Discard RLE Report Blocks SHOULD be sent in conjunction with an RTCP Discard RLE Report Blocks SHOULD be sent in conjunction with an RTCP
RR as a compound RTCP packet. RR as a compound RTCP packet.
Editor's node: is it acceptable to use one of the 'reserved' bits for
this purpose or should two block types be used?
4. XR Bytes Discarded Report Block 4. XR Bytes Discarded Report Block
The XR Bytes Discarded report block uses the following format which The XR Bytes Discarded report block uses the following format which
follows the model of the framework for performance metric development follows the model of the framework for performance metric development
[RFC6390]. [RFC6390].
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=BDR | I | Tag |E|res| block length=2 | | BT=BDR | I | Tag |E|res| block length=2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| number of bytes discarded | | number of bytes discarded |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: XR Bytes Discarded Report Block Figure 2: XR Bytes Discarded Report Block
The Interval Metric flag (I) (2 bits) is used to indicate whether the The Interval Metric flag (I) (2 bits) is used to indicate whether the
Post-Repair Loss metric is Sampled, Interval, or a Cumulative metric, discard metric is Sampled, Interval, or a Cumulative metric, that is,
that is, whether the reported value applies to the most recent whether the reported value applies to the most recent measurement
measurement interval duration between successive reports (I=10, the interval duration between successive reports (I=10, the Interval
Interval Duration) or to the accumulation period characteristic of Duration) or to the accumulation period characteristic of cumulative
cumulative measurements (I=11, the Cumulative Duration) or is a measurements (I=11, the Cumulative Duration) or is a sampled value
sampled value (I=01). Numerical values for sampled duration are (I=01).
provided in the Measurement Identifier block referenced by the tag
field below.
Measurement Identifier association (Tag) 3 bits: This field is used
to identify the Measurement Identifier block which describes the
sampled measurement. The tag in the corresponding Measurement
Identifier block has the same tag value. Note that there may be more
than one Measurement Identifier block per RTCP packet. The tag MUST
be set to 0 when using cumulative or interval durations.
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.
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 (I=0) or the number of indicating the total number of bytes discarded (I=11), or the number
bytes discarded since the last RTCP XR Bytes Discarded block was of bytes discarded since the last RTCP XR Bytes Discarded block was
sent. sent (I=10), or bytes discarded in a measurement interval (I=01)
[I-D.ietf-xrblock-rtcp-xr-meas-identity].
Bytes Discarded Report Blocks SHOULD be sent in conjunction with an Bytes Discarded Report Blocks SHOULD be sent in conjunction with an
RTCP RR as a compound RTCP packet. RTCP RR as a compound RTCP packet.
Editor's note: is it acceptable to use one of the 'reserved' bits for
this purpose or should two block types be used?
5. Protocol Operation 5. Protocol Operation
This section describes the behavior of the reporting (= receiver) RTP This section describes the behavior of the reporting (= receiver) RTP
node and the sender RTP node. node and the sender RTP node.
5.1. Reporting Node (Receiver) 5.1. Reporting Node (Receiver)
Transmission of RTCP XR Discard RLE Reports is up to the discretion Transmission of RTCP XR Discard RLE Reports is up to the discretion
of the receiver, as is the reporting granularity. However, it is of the receiver, as is the reporting granularity. However, it is
RECOMMENDED that the receiver signals all discarded packets using the RECOMMENDED that the receiver signals all discarded packets using the
skipping to change at page 10, line 13 skipping to change at page 10, line 5
Block for Discard metric Reporting", Block for Discard metric Reporting",
draft-ietf-xrblock-rtcp-xr-discard-00 (work in progress), draft-ietf-xrblock-rtcp-xr-discard-00 (work in progress),
October 2011. October 2011.
[I-D.ietf-xrblock-rtcp-xr-burst-gap-discard] [I-D.ietf-xrblock-rtcp-xr-burst-gap-discard]
Hunt, G., Clark, A., Huang, R., and W. Wu, "RTCP XR Report Hunt, G., Clark, A., Huang, R., and W. Wu, "RTCP XR Report
Block for Burst/Gap Discard metric Reporting", Block for Burst/Gap Discard metric Reporting",
draft-ietf-xrblock-rtcp-xr-burst-gap-discard-00 (work in draft-ietf-xrblock-rtcp-xr-burst-gap-discard-00 (work in
progress), October 2011. progress), October 2011.
[I-D.ietf-xrblock-rtcp-xr-meas-identity]
Hunt, G., Clark, A., and W. Wu, "Measurement Identity and
information Reporting using SDES item and XR Block",
draft-ietf-xrblock-rtcp-xr-meas-identity-01 (work in
progress), October 2011.
[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
Performance Metric Development", BCP 170, RFC 6390, Performance Metric Development", BCP 170, RFC 6390,
October 2011. October 2011.
Appendix A. Change Log Appendix A. Change Log
Note to the RFC-Editor: please remove this section prior to Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
A.1. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-00 A.1. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-00
o Changed the interval flag from 1 to 2 bits in the discarded bytes o Changed the interval flag from 1 to 2 bits in the discarded bytes
report. Also added the measurement identification tag to the report. Also added the measurement identification tag to the
block. block.
o Added this section. o Added this section.
A.2. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01
o Removed the measurement identification tag to the block.
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
Varun Singh Varun Singh
Aalto University Aalto University
School of Science and Technology School of Science and Technology
Otakaari 5 A Otakaari 5 A
Espoo, FIN 02150 Espoo, FIN 02150
Finland Finland
Email: varun@comnet.tkk.fi Email: varun@comnet.tkk.fi
URI: http://www.netlab.tkk.fi/~varun/ URI: http://www.netlab.tkk.fi/~varun/
Igor D.D. Curcio Igor D.D. Curcio
Nokia Research Center Nokia Research Center
P.O. Box 1000 (Visiokatu 1) P.O. Box 1000 (Visiokatu 1)
Tampere, FIN 33721 Tampere, FIN 33721
Finland Finland
Email: igor.curcio@nokia.com Email: igor.curcio@nokia.com
 End of changes. 15 change blocks. 
32 lines changed or deleted 30 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/