RFC 8836 on Congestion Control Requirements for Interactive Real-Time Media

rfc-editor@rfc-editor.org Mon, 18 January 2021 23:32 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE2003A13BB; Mon, 18 Jan 2021 15:32:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 UKOuPTohe6hw; Mon, 18 Jan 2021 15:32:16 -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 56EB33A1082; Mon, 18 Jan 2021 15:31:03 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 162E0F407A3; Mon, 18 Jan 2021 15:30:48 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg4MzYgb24gQ29uZ2VzdGlvbiBDb250cm9sIFJlcXVpcmVtZW50cyBmb3IgSW50ZXJhY3RpdmUgUmVhbC1UaW1lIE1lZGlh?=
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: <20210118233048.162E0F407A3@rfc-editor.org>
Date: Mon, 18 Jan 2021 15:30:48 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/vQiU91Lv_zyg_5krO2oC1Xd7v0k>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jan 2021 23:32:24 -0000

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

        
        RFC 8836

        Title:      Congestion Control Requirements for Interactive 
                    Real-Time Media 
        Author:     R. Jesup,
                    Z. Sarker, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       January 2021
        Mailbox:    randell-ietf@jesup.org,
                    Zaheduzzaman.Sarker@ericsson.com
        Pages:      10
        Updates/Obsoletes/SeeAlso:   None

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

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

        DOI:        10.17487/RFC8836

Congestion control is needed for all data transported across the
Internet, in order to promote fair usage and prevent congestion
collapse. The requirements for interactive, point-to-point real-time
multimedia, which needs low-delay, semi-reliable data delivery, are
different from the requirements for bulk transfer like FTP or bursty
transfers like web pages. Due to an increasing amount of RTP-based
real-time media traffic on the Internet (e.g., with the introduction
of the Web Real-Time Communication (WebRTC)), it is especially
important to ensure that this kind of traffic is congestion
controlled.

This document describes a set of requirements that can be used to
evaluate other congestion control mechanisms in order to figure out
their fitness for this purpose, and in particular to provide a set of
possible requirements for a real-time media congestion avoidance
technique.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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