RTP Application Interaction with Congestion Control
draft-zanaty-rmcat-app-interaction-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-03-02
Replaced by draft-ietf-rmcat-app-interaction
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
RMCAT WG                                                       M. Zanaty
Internet-Draft                                                     Cisco
Intended status: Informational                                  V. Singh
Expires: September 4, 2014                              Aalto University
                                                           S. Nandakumar
                                                                   Cisco
                                                           March 3, 2014

          RTP Application Interaction with Congestion Control
                 draft-zanaty-rmcat-app-interaction-00

Abstract

   Interactive real-time media applications that use the Real-time
   Transport Protocol (RTP) over the User Datagram Protocol (UDP) must
   use congestion control techniques above the UDP layer since it
   provides none.  This memo describes the interactions and interfaces
   necessary between the application components that relate to
   congestion control, including the RTP layer, the higher-level media
   codec control layer, and the lower-level transport interface and the
   congestion control layer.

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 September 4, 2014.

Copyright Notice

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

Zanaty, et al.          Expires September 4, 2014               [Page 1]
Internet-Draft        RMCAT Application Interaction           March 2014

   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.  Key Words for Requirements  . . . . . . . . . . . . . . . . .   3
   3.  Conceptual Model  . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Implementation Model  . . . . . . . . . . . . . . . . . . . .   5
   5.  Interfaces and Interactions . . . . . . . . . . . . . . . . .   6
     5.1.  Config - Codec Interactions . . . . . . . . . . . . . . .   6
     5.2.  Codec - RTP Interactions  . . . . . . . . . . . . . . . .   6
     5.3.  Codec - CC Interactions . . . . . . . . . . . . . . . . .   7
     5.4.  RTP - CC Interactions . . . . . . . . . . . . . . . . . .   9
     5.5.  CC - UDP Interactions . . . . . . . . . . . . . . . . . .   9
     5.6.  CC - Shared State Interactions  . . . . . . . . . . . . .  10
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   Interactive real-time media applications most commonly use RTP
   [RFC3550] over UDP [RFC0768].  Since UDP provides no form of
   congestion control, which is essential for any application deployed
   on the Internet, these RTP applications have historically implemented
   one of the following options at the application layer to address
   their congestion control requirements.

   1.  For media with relatively low packet rates and bit rates, such as
       many speech codecs, some applications use a simple form of
       congestion control that stops transmission permanently or
       temporarily after observing significant packet loss over a
       significant period of time, similar to the RTP circuit breakers
       [I-D.ietf-avtcore-rtp-circuit-breakers].

   2.  Some applications have no explicit congestion control, despite
       the clear requirements in RTP and its profiles AVP [RFC3551] and
       AVPF [RFC4585], under the expectation that users will terminate
Show full document text