RTCP Extension for Third-party Loss Report
draft-ietf-avtcore-feedback-supression-rtp-13

The information below is for an old version of the document
Document Type Active Internet-Draft (avtcore WG)
Last updated 2012-03-01 (latest revision 2012-02-22)
Replaces draft-wu-avt-retransmission-supression-rtp
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Document shepherd Magnus Westerlund
Shepherd write-up Show (last changed 2012-02-23)
IESG IESG state AD Evaluation::Revised I-D Needed
Telechat date
Responsible AD Robert Sparks
IESG note Magnus Westerlund (magnus.westerlund@ericsson.com) is the document shepherd.
Send notices to avtcore-chairs@tools.ietf.org, draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org
Network Working Group                                              Q. Wu
Internet-Draft                                                    F. Xia
Intended status: Standards Track                                 R. Even
Expires: August 26, 2012                                          Huawei
                                                       February 23, 2012

               RTCP Extension for Third-party Loss Report
             draft-ietf-avtcore-feedback-supression-rtp-13

Abstract

   In a large RTP session using the RTCP feedback mechanism defined in
   RFC 4585, a feedback target may experience transient overload if some
   event causes a large number of receivers to send feedback at once.
   This overload is usually avoided by ensuring that feedback reports
   are forwarded to all receivers, allowing them to avoid sending
   duplicate feedback reports.  However, there are cases where it is not
   recommended to forward feedback reports, and this may allow feedback
   implosion.  This memo discusses these cases and defines a new RTCP
   third-party loss report that can be used to inform receivers that the
   feedback target is aware of some loss event, allowing them to
   suppress feedback.  Associated SDP signalling is also defined.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 26, 2012.

Copyright Notice

   Copyright (c) 2012 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

Wu, et al.               Expires August 26, 2012                [Page 1]
Internet-Draft           Third Party Loss Report           February 2012

   (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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Requirements Notation  . . . . . . . . . . . . . . . . . . . .  3
   3.  Protocol Overview  . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Format of RTCP Feedback Messages . . . . . . . . . . . . . . .  5
     4.1.  Transport Layer Feedback:  Third-party Loss Report . . . .  5
     4.2.  Payload Specific Feedback: Third-party Loss Report . . . .  6
   5.  SDP Signaling  . . . . . . . . . . . . . . . . . . . . . . . .  7
   6.  Example Use Cases  . . . . . . . . . . . . . . . . . . . . . .  8
     6.1.  Source Specific Multicast (SSM) use case . . . . . . . . .  8
     6.2.  Unicast based Rapid Acquisition of Multicast Stream
           (RAMS) use case  . . . . . . . . . . . . . . . . . . . . .  8
     6.3.  RTP Transport Translator use case  . . . . . . . . . . . .  9
     6.4.  Multipoint Control Unit (MCU) use case . . . . . . . . . .  9
     6.5.  Mixer use case . . . . . . . . . . . . . . . . . . . . . .  9
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   8.  IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 10
   9.  Acknowledgement  . . . . . . . . . . . . . . . . . . . . . . . 11
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 11
     10.2. Informative References . . . . . . . . . . . . . . . . . . 12
   Appendix A.  Change Log  . . . . . . . . . . . . . . . . . . . . . 13
     A.1.  draft-ietf-avtcore-feedback-suppression-rtp-01 . . . . . . 13
     A.2.  draft-ietf-avtcore-feedback-suppression-rtp-02 . . . . . . 13
     A.3.  draft-ietf-avtcore-feedback-suppression-rtp-03 . . . . . . 13
     A.4.  draft-ietf-avtcore-feedback-suppression-rtp-04 . . . . . . 14
     A.5.  draft-ietf-avtcore-feedback-suppression-rtp-05 . . . . . . 14
     A.6.  draft-ietf-avtcore-feedback-suppression-rtp-06 . . . . . . 15
     A.7.  draft-ietf-avtcore-feedback-suppression-rtp-07 . . . . . . 15
Show full document text