[rmcat] RFC 8382 on Shared Bottleneck Detection for Coupled Congestion Control for RTP Media

rfc-editor@rfc-editor.org Tue, 26 June 2018 06:00 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB9EF1292AD; Mon, 25 Jun 2018 23:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I4-jcLKhWEcq; Mon, 25 Jun 2018 23:00:46 -0700 (PDT)
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 EAAF9127AC2; Mon, 25 Jun 2018 23:00:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0F676B8131F; Mon, 25 Jun 2018 23:00:43 -0700 (PDT)
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: <20180626060043.0F676B8131F@rfc-editor.org>
Date: Mon, 25 Jun 2018 23:00:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/E4YfVinC7dp1DUvQGI8AkpOfT0M>
Subject: [rmcat] RFC 8382 on Shared Bottleneck Detection for Coupled Congestion Control for RTP Media
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 26 Jun 2018 06:00:50 -0000

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

        
        RFC 8382

        Title:      Shared Bottleneck Detection for
                    Coupled Congestion Control for RTP Media 
        Author:     D. Hayes, Ed.,
                    S. Ferlin,
                    M. Welzl,
                    K. Hiorth
        Status:     Experimental
        Stream:     IETF
        Date:       June 2018
        Mailbox:    davidh@simula.no, 
                    simone@ferlin.io, 
                    michawe@ifi.uio.no,
                    kristahi@ifi.uio.no
        Pages:      25
        Characters: 49095
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmcat-sbd-11.txt

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

        DOI:        10.17487/RFC8382

This document describes a mechanism to detect whether end-to-end data
flows share a common bottleneck.  This mechanism relies on summary
statistics that are calculated based on continuous measurements and
used as input to a grouping algorithm that runs wherever the
knowledge is needed.

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
  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