RTP Control Protocol (RTCP) Feedback for Congestion Control
draft-dt-rmcat-feedback-message-03

Document Type Active Internet-Draft (rmcat WG)
Last updated 2017-07-17
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
IETF RMCAT Working Group                                       Z. Sarker
Internet-Draft                                               Ericsson AB
Intended status: Standards Track                              C. Perkins
Expires: January 17, 2018                          University of Glasgow
                                                                V. Singh
                                                            callstats.io
                                                              M. Ramalho
                                                           Cisco Systems
                                                           July 16, 2017

      RTP Control Protocol (RTCP) Feedback for Congestion Control
                   draft-dt-rmcat-feedback-message-03

Abstract

   This document describes a feedback message intended to enable
   congestion control for interactive real-time traffic.  The RTP Media
   Congestion Avoidance Techniques (RMCAT) Working Group formed a design
   team to analyze feedback requirements from various congestion control
   algorithms and to design a generic feedback message to help ensure
   interoperability across those algorithms.  The feedback message is
   designed for a sender-based congestion control, which means the
   receiver of the media will send necessary feedback to the sender of
   the media to perform the congestion control at the sender.

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 January 17, 2018.

Copyright Notice

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

Sarker, et al.          Expires January 17, 2018                [Page 1]
Internet-Draft     Congestion Control Feedback in RTCP         July 2017

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Feedback Message  . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  RTCP XR Block for Reporting Congestion Control Feedback .   4
     3.2.  RTP/AVPF Transport Layer Feedback for Congestion Control    6
   4.  Feedback Frequency and Overhead . . . . . . . . . . . . . . .   7
   5.  Design Rationale  . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  RTP/AVPF Transport Layer Feedback Message . . . . . . . .   9
     7.2.  RTCP XR Report Blocks . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   For interactive real-time traffic the typical protocol choice is
   Realtime Transport Protocol (RTP) over User Datagram Protocol (UDP).
   RTP does not provide any guarantee of Quality of Service (QoS),
   reliable or timely delivery and expects the underlying transport
   protocol to do so.  UDP alone certainly does not meet that
   expectation.  However, RTP Control Protocol (RTCP) provides a
   mechanism to periodically send transport and media metrics to the
   media sender which can be utilized and extended for the purposes of
   RMCAT congestion control.  For a congestion control algorithm which
   operates at the media sender, RTCP messages can be transmitted from
Show full document text