[rmcat] RFC 8699 on Coupled Congestion Control for RTP Media

rfc-editor@rfc-editor.org Fri, 31 January 2020 17:38 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id EE4E2120A96; Fri, 31 Jan 2020 09:38:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Y7uGkixm-lF8; Fri, 31 Jan 2020 09:38:57 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 382E712021C; Fri, 31 Jan 2020 09:38:57 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4423DF406F0; Fri, 31 Jan 2020 09:38:49 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rmcat@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200131173849.4423DF406F0@rfc-editor.org>
Date: Fri, 31 Jan 2020 09:38:49 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/w60B86_r3pvq-G_hM05JuXhwdrs>
Subject: [rmcat] =?utf-8?q?RFC_8699_on_Coupled_Congestion_Control_for_RTP?= =?utf-8?q?_Media?=
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2020 17:38:59 -0000

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

        RFC 8699

        Title:      Coupled Congestion Control for RTP Media 
        Author:     S. Islam, 
                    M. Welzl,
                    S. Gjessing
        Status:     Experimental
        Stream:     IETF
        Date:       UNKNOWN 
        Mailbox:    safiquli@ifi.uio.no, 
        Pages:      20
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmcat-coupled-cc-09.txt

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

        DOI:        10.17487/RFC8699

When multiple congestion-controlled Real-time Transport Protocol
(RTP) sessions traverse the same network bottleneck, combining their
controls can improve the total on-the-wire behavior in terms of
delay, loss, and fairness. This document describes such a method for
flows that have the same sender, in a way that is as flexible and
simple as possible while minimizing the number of changes needed to
existing RTP applications. This document also specifies how to apply
the method for the Network-Assisted Dynamic Adaptation (NADA)
congestion control algorithm and provides suggestions on how to apply
it to other congestion control algorithms.

This document is a product of the RTP Media Congestion Avoidance Techniques Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

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