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

Colin Perkins <csp@csperkins.org> Wed, 20 July 2016 08:12 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 17D8F12DAD7 for <avt@ietfa.amsl.com>; Wed, 20 Jul 2016 01:12:58 -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] 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 3OyZnZUnj69k for <avt@ietfa.amsl.com>; Wed, 20 Jul 2016 01:12:56 -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 EF6D412B039 for <avt@ietf.org>; Wed, 20 Jul 2016 01:12:55 -0700 (PDT)
Received: from [2001:67c:370:176:ed9f:ac49:af49:3558] (port=51742) 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 1bPmcJ-0003S5-3O; Wed, 20 Jul 2016 09:12:48 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20160720080244.22515.31653.idtracker@ietfa.amsl.com>
Date: Wed, 20 Jul 2016 10:12:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E28BD8AB-EB51-41A1-9FE9-D8420F22AF3C@csperkins.org>
References: <20160720080244.22515.31653.idtracker@ietfa.amsl.com>
To: IETF AVTCore WG <avt@ietf.org>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/qy0EbpLev66I0FQ2Nm0opaEvsbQ>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "Black, David" <david.black@emc.com>, "Mirja Kuehlewind \(IETF\)" <ietf@kuehlewind.net>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-17.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 20 Jul 2016 08:12:58 -0000

This version replaces the discussion of ECN in Section 7 with a statement that there’s no consensus on on how the receipt of ECN feedback will impact the congestion circuit breaker, or indeed whether the congestion circuit breaker ought to take ECN feedback into account. 

Hopefully this is now ready to proceed to publication.

Colin




> On 20 Jul 2016, at 10:02, 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-17.txt
> 	Pages           : 25
> 	Date            : 2016-07-20
> 
> 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 these applications, then network congestion can
>   lead to uncontrolled packet loss, and a resulting deterioration of
>   the user's multimedia experience.  The congestion control algorithm
>   acts as a safety measure, stopping RTP flows from using excessive
>   resources, and protecting the network from overload.  At the time of
>   this writing, however, while there are several proprietary solutions,
>   there is no standard algorithm for congestion control of interactive
>   RTP flows.
> 
>   This document does not propose a congestion control algorithm.  It
>   instead defines a minimal set of RTP circuit breakers: conditions
>   under which an RTP sender needs to stop transmitting media data, to
>   protect the network from excessive congestion.  It is expected that,
>   in the absence of long-lived excessive congestion, RTP applications
>   running on best-effort IP networks will be able to operate without
>   triggering these circuit breakers.  To avoid triggering the RTP
>   circuit breaker, any standards-track congestion control algorithms
>   defined for RTP will need to operate within the envelope set by these
>   RTP circuit breaker algorithms.
> 
> 
> 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-17
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-circuit-breakers-17
> 
> 
> 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/