[AVTCORE] RFC 8083 on Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions

rfc-editor@rfc-editor.org Tue, 07 March 2017 22:16 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B0C9129519; Tue, 7 Mar 2017 14:16:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B_GpEOLIiqap; Tue, 7 Mar 2017 14:16:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D11F1294E1; Tue, 7 Mar 2017 14:16:01 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0C77CB81990; Tue, 7 Mar 2017 14:16:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170307221600.0C77CB81990@rfc-editor.org>
Date: Tue, 7 Mar 2017 14:16:00 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/UWOIjCWNS-clLe92rfa3fPsHpwg>
Cc: drafts-update-ref@iana.org, avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVTCORE] RFC 8083 on Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Mar 2017 22:16:06 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8083

        Title:      Multimedia Congestion Control: Circuit Breakers 
                    for Unicast RTP Sessions 
        Author:     C. Perkins, V. Singh
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    csp@csperkins.org, 
                    varun@callstats.io
        Pages:      25
        Characters: 67197
        Updates:    RFC 3550

        I-D Tag:    draft-ietf-avtcore-rtp-circuit-breakers-18.txt

        URL:        https://www.rfc-editor.org/info/rfc8083

        DOI:        10.17487/RFC8083

The Real-time Transport Protocol (RTP) is widely used in telephony,
video conferencing, and telepresence applications.  Such applications
are often run on best-effort UDP/IP networks.  If congestion control
is not implemented in these applications, then network congestion can
lead to uncontrolled packet loss and a resulting deterioration of the
user's multimedia experience.  The congestion control algorithm acts
as a safety measure by stopping RTP flows from using excessive
resources and protecting the network from overload.  At the time of
this writing, however, while there are several proprietary solutions,
there is no standard algorithm for congestion control of interactive
RTP flows.

This document does not propose a congestion control algorithm.  It
instead defines a minimal set of RTP circuit breakers: conditions
under which an RTP sender needs to stop transmitting media data to
protect the network from excessive congestion.  It is expected that,
in the absence of long-lived excessive congestion, RTP applications
running on best-effort IP networks will be able to operate without
triggering these circuit breakers.  To avoid triggering the RTP
circuit breaker, any Standards Track congestion control algorithms
defined for RTP will need to operate within the envelope set by these
RTP circuit breaker algorithms.

This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC