datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Post-Repair Loss RLE Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)
RFC 5725

Internet Engineering Task Force (IETF)                          A. Begen
Request for Comments: 5725                                        D. Hsu
Category: Standards Track                                       M. Lague
ISSN: 2070-1721                                                    Cisco
                                                           February 2010

               Post-Repair Loss RLE Report Block Type for
           RTP Control Protocol (RTCP) Extended Reports (XRs)

Abstract

   This document defines a new report block type within the framework of
   RTP Control Protocol (RTCP) Extended Reports (XRs).  One of the
   initial XR report block types is the Loss Run Length Encoding (RLE)
   Report Block.  This report conveys information regarding the
   individual Real-time Transport Protocol (RTP) packet receipt and loss
   events experienced during the RTCP interval preceding the
   transmission of the report.  The new report, which is referred to as
   the Post-repair Loss RLE report, carries information regarding the
   packets that remain lost after all loss-repair methods are applied.
   By comparing the RTP packet receipts/losses before and after the loss
   repair is completed, one can determine the effectiveness of the loss-
   repair methods in an aggregated fashion.  This document also defines
   the signaling of the Post-repair Loss RLE report in the Session
   Description Protocol (SDP).

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc5725.

Begen, et al.                Standards Track                    [Page 1]
RFC 5725         Post-Repair Loss RLE Report Block Type    February 2010

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Requirements Notation . . . . . . . . . . . . . . . . . . . . . 4
   3.  Post-Repair Loss RLE Report Block . . . . . . . . . . . . . . . 4
   4.  Session Description Protocol Signaling  . . . . . . . . . . . . 6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 8
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 8

Begen, et al.                Standards Track                    [Page 2]
RFC 5725         Post-Repair Loss RLE Report Block Type    February 2010

1.  Introduction

   The RTP Control Protocol (RTCP) is the out-of-band control protocol
   for applications that are using the Real-time Transport Protocol
   (RTP) for media delivery and communications [RFC3550].  RTCP allows
   RTP entities to monitor data delivery and provides them minimal

[include full document text]