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

Colin Perkins <csp@csperkins.org> Mon, 23 March 2015 21:18 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 BC7921A1AE3 for <avt@ietfa.amsl.com>; Mon, 23 Mar 2015 14:18:33 -0700 (PDT)
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 P7w0dc4RoPqp for <avt@ietfa.amsl.com>; Mon, 23 Mar 2015 14:18:32 -0700 (PDT)
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 389DB1B29E7 for <avt@ietf.org>; Mon, 23 Mar 2015 14:18:30 -0700 (PDT)
Received: from [130.209.254.19] (port=52307 helo=vpn19.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1Ya9jw-0002D6-5Q for avt@ietf.org; Mon, 23 Mar 2015 21:18:28 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20150323211310.19157.5784.idtracker@ietfa.amsl.com>
Date: Mon, 23 Mar 2015 16:18:23 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AED2010-30C2-4FFB-A71A-D31CBA28F29D@csperkins.org>
References: <20150323211310.19157.5784.idtracker@ietfa.amsl.com>
To: "avt@ietf.org WG" <avt@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/I1VwcLGx4RPP5rAji6SWeDaZZ3M>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-10.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: <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: Mon, 23 Mar 2015 21:18:33 -0000

This version fixes the table in Section 4.5, changes the CB_INTERVAL definition for RTP/AVPF to be max(T_rr_interval, Td), and adds a reference to the TSVWG generic transport circuit breaker draft.

Colin




On 23 Mar 2015, at 16:13, 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
>        Authors         : Colin Perkins
>                          Varun Singh
> 	Filename        : draft-ietf-avtcore-rtp-circuit-breakers-10.txt
> 	Pages           : 22
> 	Date            : 2015-03-23
> 
> 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-10
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-circuit-breakers-10
> 
> 
> 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/