Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-18.txt
Colin Perkins <csp@csperkins.org> Thu, 18 August 2016 17:28 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 EBAE112D85F for <avt@ietfa.amsl.com>; Thu, 18 Aug 2016 10:28:51 -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 6sAEbNJiTY0Y for <avt@ietfa.amsl.com>; Thu, 18 Aug 2016 10:28:46 -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 2E0C512DA07 for <avt@ietf.org>; Thu, 18 Aug 2016 10:28:45 -0700 (PDT)
Received: from [81.187.2.149] (port=35444 helo=[192.168.0.91]) 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 1baR7P-0000Su-Js for avt@ietf.org; Thu, 18 Aug 2016 18:28:43 +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: <147154086624.27840.13399354322098770056.idtracker@ietfa.amsl.com>
Date: Thu, 18 Aug 2016 18:28:37 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <155AFB36-0048-429B-BD08-7E26AB2C4C6C@csperkins.org>
References: <147154086624.27840.13399354322098770056.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/zB1hcLCiRSDbM6KcRehekCSjjsw>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-18.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: Thu, 18 Aug 2016 17:28:52 -0000
This version includes the change Varun suggested on the list on 26 July (“In section 4.5, I would propose reshuffling the statements a bit to make the guidance more appropriate”): OLD: What it means to cease transmission depends on the application. The intention is that the application will stop sending RTP data packets on a particular 5-tuple (transport protocol, source and destination ports, source and destination IP addresses), until whatever network problem that triggered the RTP circuit breaker has dissipated. This could mean stopping a single RTP flow, or it could mean that multiple bundled RTP flows are stopped. NEW: What it means to cease transmission depends on the application. This could mean stopping a single RTP flow, or it could mean that multiple bundled RTP flows are stopped. The intention is that the application will stop sending RTP data packets on a particular 5-tuple (transport protocol, source and destination ports, source and destination IP addresses), until whatever network problem that triggered the RTP circuit breaker has dissipated. There are no other changes. Colin > On 18 Aug 2016, at 18:21, 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-18.txt > Pages : 25 > Date : 2016-08-18 > > 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-18 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-circuit-breakers-18 > > > 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/
- Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-… Colin Perkins
- [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circ… internet-drafts