draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-04.txt   draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05.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: January 6, 2013 I. Curcio Expires: June 22, 2013 I. Curcio
Nokia Research Center Nokia Research Center
July 5, 2012 December 19, 2012
RTP Control Protocol (RTCP) Extended Reports (XR) for Run Length RTP Control Protocol (RTCP) Extended Reports (XR) for Run Length
Encoding (RLE) of Discarded Packets Encoding (RLE) of Discarded Packets
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-04.txt draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05.txt
Abstract Abstract
The RTP Control Protocol (RTCP) is used in conjunction with the Real- The RTP Control Protocol (RTCP) is used in conjunction with the Real-
time Transport Protocol (RTP) in to provide a variety of short-term time Transport Protocol (RTP) in to provide a variety of short-term
and long-term reception statistics. The available reporting may and long-term reception statistics. The available reporting may
include aggregate information across longer periods of time as well include aggregate information across longer periods of time as well
as individual packet reporting. This document specifies a per-packet as individual packet reporting. This document specifies a per-packet
report metric capturing individual packets discarded from the jitter report metric capturing individual packets discarded from the jitter
buffer after successful reception. 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 January 6, 2013. This Internet-Draft will expire on June 22, 2013.
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 20 skipping to change at page 2, line 20
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 . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Reporting Node (Receiver) . . . . . . . . . . . . . . . . 7 5.1. Reporting Node (Receiver) . . . . . . . . . . . . . . . . 7
5.2. Media Sender . . . . . . . . . . . . . . . . . . . . . . . 7 5.2. Media Sender . . . . . . . . . . . . . . . . . . . . . . . 7
6. SDP signaling . . . . . . . . . . . . . . . . . . . . . . . . 8 6. SDP signaling . . . . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8.1. XR Report Block Registration . . . . . . . . . . . . . . . 9 8.1. XR Report Block Registration . . . . . . . . . . . . . . . 9
8.2. SDP Parameter Registration . . . . . . . . . . . . . . . . 9 8.2. SDP Parameter Registration . . . . . . . . . . . . . . . . 9
8.3. Contact information for IANA registrations . . . . . . . . 9 8.3. Contact information for IANA registrations . . . . . . . . 9
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
10.1. Normative References . . . . . . . . . . . . . . . . . . . 9 10.1. Normative References . . . . . . . . . . . . . . . . . . . 9
10.2. Informative References . . . . . . . . . . . . . . . . . . 10 10.2. Informative References . . . . . . . . . . . . . . . . . . 10
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 . . . . 11 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 . . . . 11 draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01 . . . . 10
A.3. changes in A.3. changes in
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02 . . . . 11 draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02 . . . . 11
A.4. changes in A.4. changes in
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-03 . . . . 11 draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-03 . . . . 11
A.5. changes in A.5. changes in
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-04 . . . . 11 draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-04 . . . . 11
A.6. changes in
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05 . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 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 (RTCP) which
periodic feedback about the media streams received in a specific provides periodic feedback about the media streams received in a
duration. In addition, RTCP can be used for timely feedback about specific duration. In addition, RTCP can be used for timely feedback
individual events (e.g., packet loss) [RFC4585]. Both long-term and about individual events to report (e.g., packet loss) [RFC4585].
short-term feedback enable a sender to adapt its media transmission Both long-term and short-term feedback enable a sender to adapt its
and/or encoding dynamically to the observed path characteristics. media transmission and/or encoding dynamically to the observed path
characteristics.
RFC3611 [RFC3611] defines RTCP Extended Reports as a detailed RFC3611 [RFC3611] defines RTCP Extended Reports as a detailed
reporting framework to provide more than just the coarse RR reporting framework to provide more than just the coarse RR
statistics. The detailed reporting may enable a sender to react more statistics. The detailed reporting may enable a sender to react more
appropriately to the observed networking conditions as these can be appropriately to the observed networking conditions as these can be
characterized better, although at the expense of extra overhead. characterized better, although at the expense of extra overhead.
Among many other report blocks, RFC3611 specifies the Loss RLE block Among many other report blocks, RFC3611 specifies the Loss RLE block
which reports runs of packets received and lost with the granularity which reports runs of packets received and lost with the granularity
of individual packets. This can help both error recovery and path of individual packets. This can help both error recovery and path
skipping to change at page 7, line 8 skipping to change at page 7, line 8
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 Interval Metric flag (I=11) is set, the value in the field If Interval Metric flag (I=11) is set, the value in the field
indicates the number of bytes discarded from the start of the indicates the number of bytes discarded from the start of the
session, if Interval Metric flag (I=01) is set, it indicates the session, if Interval Metric flag (I=01) is set, it indicates the
number of bytes discarded since the last RTCP XR Byte Discarded Block number of bytes discarded since the last RTCP XR Byte Discarded Block
was received. was received.
If the XR block follows a measurement identity block If the XR block follows a measurement identity block [RFC6776] in the
[I-D.ietf-xrblock-rtcp-xr-meas-identity] in the same RTCP compound same RTCP compound packet then the cumulative (I=11) or the interval
packet then the cumulative (I=11) or the interval (I=10) for this (I=10) for this report block corresponds to the values of the
report block corresponds to the values of the "measurement duration" "measurement duration" in the measurement information block.
in the measurement information block.
If the receiver sends the Bytes Discarded Report Block without the If the receiver sends the Bytes Discarded Report Block without the
measurement identity block then the discard block MUST be sent in measurement identity block then the discard block MUST be sent in
conjunction with an RTCP RR as a compound RTCP packet. conjunction with an RTCP RR as a compound RTCP packet.
5. Protocol Operation 5. Protocol Operation
This section describes the behavior of the reporting (= receiver) This section describes the behavior of the reporting (= receiver)
node and the media sender. node and the media sender.
skipping to change at page 8, line 7 skipping to change at page 8, line 7
nor can the sender rely on a regular generation pattern from the nor can the sender rely on a regular generation pattern from the
receiver side. receiver side.
However, if the sender receives any RTCP reports but no Discard RLE However, if the sender receives any RTCP reports but no Discard RLE
report blocks and is aware that the receiver supports Discard RLE report blocks and is aware that the receiver supports Discard RLE
report blocks, it MAY assume that no packets were discarded at the report blocks, it MAY assume that no packets were discarded at the
receiver. receiver.
The sender SHOULD accept the Bytes Discarded Report Block only if it The sender SHOULD accept the Bytes Discarded Report Block only if it
is received in a compound RTCP receiver report or if it is preceded is received in a compound RTCP receiver report or if it is preceded
by a measurement identity block by a measurement identity block [RFC6776]. Under all other
[I-D.ietf-xrblock-rtcp-xr-meas-identity]. Under all other
circumstances it MUST ignore the block. circumstances it MUST ignore the block.
6. SDP signaling 6. SDP signaling
The report blocks specified in this document define extensions to
RTCP XR reporting. Whether or not this specific extended report is
sent is left to the discretion of the receiver. Its presence may
enable better operation of the sender since more detailed information
is available. Not providing this information will make the sender
rely on other RTCP reports.
A participant of a media session MAY use SDP to signal its support A participant of a media session MAY use SDP to signal its support
for this attribute. In this case, the RTCP XR attribute as defined for the two report blocks specified in this document or use them
in RFC3611 [RFC3611] MUST be used. The SDP RFC4566 [RFC4566] without any prior signaling (see section 5 of [RFC3611]).
attribute 'xr-format' defined in RFC3611 is augmented as described in
the following to indicate the RLE discard metric and bytes discarded For signaling in SDP, the RTCP XR attribute as defined in [RFC3611]
metric. MUST be used. The SDP [RFC4566] attribute 'xr-format' defined in
RFC3611 is augmented as described in the following to indicate the
RLE discard metric and bytes discarded metric.
rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)]
CRLF ; defined in [RFC3611] CRLF ; defined in [RFC3611]
xr-format =/ xr-discard-rle xr-format =/ xr-discard-rle
/ xr-discard-bytes / xr-discard-bytes
xr-discard-rle = "discard-rle" xr-discard-rle = "discard-rle"
xr-discard-bytes = "discard-bytes" xr-discard-bytes = "discard-bytes"
The parameter 'discard-rle' MUST be used to indicate support for the The parameter 'discard-rle' MUST be used to indicate support for the
Discard RLE Report Block defined in Section 3, the parameter Discard RLE Report Block defined in Section 3, the parameter
'discard-bytes' to indicate support for the Bytes Discarded Report 'discard-bytes' to indicate support for the Bytes Discarded Report
Block defined in Section 4 Block defined in Section 4
For signaling support of the RLE discard metric and bytes discarded When SDP is used in Offer/Answer context, the mechanism defined in
metric, the rules defined in RFC3611 apply. Generally, senders and [RFC3611] for unilateral "rtcp-xr" attribute parameters applies (see
receivers SHOULD indicate this capability if they support these section 5.2 of [RFC3611]).
metrics and would like to use it in the specific media session being
signaled. The receiver MAY decide not to send discard information
unless it knows about the sender's support to save on RTCP reporting
bandwidth.
A participant in a media session MAY use the two report blocks
specified in this document without any explicit (SDP) signaling.
7. Security Considerations 7. Security Considerations
The security considerations of RFC3550 [RFC3550], RFC3611 [RFC3611], The security considerations of [RFC3550], [RFC3611], and [RFC4585]
and RFC4585 [RFC4585] apply. Since this document offers only a more apply. Since this document offers only a more precise reporting for
precise reporting for an already existing metric, no further security an already existing metric, no further security implications are
implications are foreseen. foreseen.
8. IANA Considerations 8. IANA Considerations
New block types for RTCP XR are subject to IANA registration. For New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to general guidelines on IANA considerations for RTCP XR, refer to
RFC3611 [RFC3611]. [RFC3611].
8.1. XR Report Block Registration 8.1. XR Report Block Registration
This document extends the IANA "RTCP XR Block Type Registry" by two This document extends the IANA "RTP Control Protocol Extended Reports
new values: DRLE and BDR. (RTCP XR) Block Type Registry" by two new values: DRLE and BDR.
[Note to RFC Editor: please replace DRLE and BDR with the IANA [Note to RFC Editor: please replace DRLE and BDR with the IANA
provided RTCP XR block type for this block here and in the diagrams provided RTCP XR block type for this block here and in the diagrams
above. Please remove this note prior to publication as an RFC.] above. Please remove this note prior to publication as an RFC.]
8.2. SDP Parameter Registration 8.2. SDP Parameter Registration
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". "RTP Control Protocol Extended Reports (RTCP XR) Session Description
Protocol (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. Acknowledgements 9. Acknowledgements
Thanks to Qin Wu, Colin Perkins, Dan Romascanu, and Roni Even for Thanks to Qin Wu, Colin Perkins, Dan Romascanu, Roni Even and Dan
providing valuable feedback on earlier versions of this draft Wing for providing valuable feedback on earlier versions of this
draft
10. References 10. References
10.1. Normative References 10.1. 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.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", RFC 3611,
November 2003.
[RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey,
"Extended RTP Profile for Real-time Transport Control "Extended RTP Profile for Real-time Transport Control
Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585,
July 2006. July 2006.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", RFC 3611,
November 2003.
[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-07 (work in
progress), January 2012.
[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.
[RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information
Reporting Using a Source Description (SDES) Item and an
RTCP Extended Report (XR) Block", RFC 6776, October 2012.
10.2. Informative References 10.2. Informative References
[I-D.ietf-xrblock-rtcp-xr-discard] [I-D.ietf-xrblock-rtcp-xr-discard]
Hunt, G., Clark, A., Zorn, G., and W. Wu, "RTCP XR Report Clark, A., Zorn, G., and W. Wu, "RTP Control Protocol
Block for Discard metric Reporting", (RTCP) Extended Report (XR) Block for Discard Count metric
draft-ietf-xrblock-rtcp-xr-discard-04 (work in progress), Reporting", draft-ietf-xrblock-rtcp-xr-discard-11 (work in
December 2011. progress), December 2012.
[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 Clark, A., Huang, R., and W. Wu, "RTP Control
Block for Burst/Gap Discard metric Reporting", Protocol(RTCP) Extended Report (XR) Block for Burst/Gap
draft-ietf-xrblock-rtcp-xr-burst-gap-discard-03 (work in Discard metric Reporting",
progress), October 2011. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 (work in
progress), December 2012.
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
skipping to change at page 11, line 24 skipping to change at page 11, line 14
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 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 explanation for block length in bytes discarded block.
o Added an acknowledgement section o Added an acknowledgement section.
A.5. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-04 A.5. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-04
o Added Block Type definition to each XRBlock o Added Block Type definition to each XRBlock.
o Made changes requested in WGLC o Made changes requested in WGLC.
A.6. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05
o Made changes requested by SDP directorate.
Authors' Addresses Authors' Addresses
Joerg Ott Joerg Ott
Aalto University Aalto University
School of Electrical Engineering
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 Electrical Engineering
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 3)
Tampere, FIN 33721 Tampere, FIN 33721
Finland Finland
Email: igor.curcio@nokia.com Email: igor.curcio@nokia.com
 End of changes. 31 change blocks. 
78 lines changed or deleted 73 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/