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

Colin Perkins <csp@csperkins.org> Thu, 18 July 2013 15:20 UTC

Return-Path: <csp@csperkins.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 EB4D221E8118 for <avt@ietfa.amsl.com>; Thu, 18 Jul 2013 08:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level:
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRiXcVhhKVoB for <avt@ietfa.amsl.com>; Thu, 18 Jul 2013 08:20:01 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [93.93.130.6]) by ietfa.amsl.com (Postfix) with ESMTP id 29D6221E811B for <avt@ietf.org>; Thu, 18 Jul 2013 08:19:56 -0700 (PDT)
Received: from [130.209.247.112] (port=59229 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1Uzpzk-0007rk-7H for avt@ietf.org; Thu, 18 Jul 2013 16:19:55 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20130715185534.31264.26535.idtracker@ietfa.amsl.com>
Date: Thu, 18 Jul 2013 16:19:51 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <15912DF9-1145-4099-9F00-BC1436859D6A@csperkins.org>
References: <20130715185534.31264.26535.idtracker@ietfa.amsl.com>
To: avt@ietf.org
X-Mailer: Apple Mail (2.1508)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-03.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 18 Jul 2013 15:20:06 -0000

This is a relatively minor update, based on comments received during the last meeting. Changes include:

- In Section 4.3, reorder the text to be clearer that the sender is allowed to reduce it's sending rate by a factor of ten when the congestion circuit breaker fires, to see if this resolves the problem, before it has to cease transmission.

- In Section 4.2 and Section 4.3, add some text about sessions with a large enough number of media streams that the receivers has to generate round-robin RTCP reception reports.

- In Section 4.3, clarify what RTCP reporting interval is used to trigger the circuit breaker

- Add Section 7 on the Impact of RTCP Reporting Groups.

There are also some minor editorial fixes.

Colin


On 15 Jul 2013, at 19:55, 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 Working Group of the IETF.
> 
> 	Title           : Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions
> 	Author(s)       : Colin Perkins
>                          Varun Singh
> 	Filename        : draft-ietf-avtcore-rtp-circuit-breakers-03.txt
> 	Pages           : 17
> 	Date            : 2013-07-15
> 
> 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 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:
> http://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-03
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-circuit-breakers-03
> 
> 
> 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
http://csperkins.org/