Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-12.txt

Colin Perkins <csp@csperkins.org> Tue, 09 February 2016 15:03 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D977E1A90E9 for <avt@ietfa.amsl.com>; Tue, 9 Feb 2016 07:03:06 -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] autolearn=ham
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 xW7qh9UVXe5f for <avt@ietfa.amsl.com>; Tue, 9 Feb 2016 07:03:04 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A42671A90ED for <avt@ietf.org>; Tue, 9 Feb 2016 07:03:04 -0800 (PST)
Received: from [130.209.247.112] (port=53581 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1aT9oj-00013b-IZ; Tue, 09 Feb 2016 15:03:02 +0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20160209150104.21383.43407.idtracker@ietfa.amsl.com>
Date: Tue, 09 Feb 2016 15:02:59 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <1DE78022-1DF4-479E-B1D0-EC9B862FD83E@csperkins.org>
References: <20160209150104.21383.43407.idtracker@ietfa.amsl.com>
To: IETF AVTCore WG <avt@ietf.org>
X-Mailer: Apple Mail (2.3112)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/31RUxNbKfiTOYinm-4-A2tgq364>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Meral Shirazipour <meral.shirazipour@ericsson.com>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-12.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Feb 2016 15:03:07 -0000

This version is intended to address the review comments from Gorry Fairhurst and Meral Shirazipour. There are a number of clarifications, but no protocol changes. 

Colin



> On 9 Feb 2016, at 15:01, Internet-Drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Audio/Video Transport Core Maintenance of the IETF.
> 
>        Title           : Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions
>        Authors         : Colin Perkins
>                          Varun Singh
> 	Filename        : draft-ietf-avtcore-rtp-circuit-breakers-12.txt
> 	Pages           : 24
> 	Date            : 2016-02-09
> 
> Abstract:
>   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 the applications, then network congestion will
>   deteriorate the user's multimedia experience.  This acts as a safety
>   measure to prevent starvation of network resources denying other
>   flows from access to the Internet, such measures are essential for an
>   Internet that is heterogeneous and for traffic that is hard to
>   predict in advance.  This document does not propose a congestion
>   control algorithm; instead, it defines a minimal set of RTP circuit-
>   breakers.  Circuit-breakers are conditions under which an RTP sender
>   needs to stop transmitting media data in order to protect the network
>   from excessive congestion.  It is expected that, in the absence of
>   severe congestion, all RTP applications running on best-effort IP
>   networks will be able to run without triggering these circuit
>   breakers.  Any future RTP congestion control specification will be
>   expected to operate within the constraints defined by these circuit
>   breakers.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-12
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-circuit-breakers-12
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



-- 
Colin Perkins
https://csperkins.org/