Re: [ledbat] [R-C] LEDBAT vs RTCWeb
Randell Jesup <randell-ietf@jesup.org> Thu, 26 April 2012 17:13 UTC
Return-Path: <randell-ietf@jesup.org>
X-Original-To: ledbat@ietfa.amsl.com
Delivered-To: ledbat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E86D921E8124 for <ledbat@ietfa.amsl.com>; Thu, 26 Apr 2012 10:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.254
X-Spam-Level:
X-Spam-Status: No, score=-2.254 tagged_above=-999 required=5 tests=[AWL=0.344, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 cfRw8AhubZsq for <ledbat@ietfa.amsl.com>; Thu, 26 Apr 2012 10:13:57 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id BF7BD21E80E3 for <ledbat@ietf.org>; Thu, 26 Apr 2012 10:13:57 -0700 (PDT)
Received: from pool-108-16-41-249.phlapa.fios.verizon.net ([108.16.41.249] helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <randell-ietf@jesup.org>) id 1SNSGG-0007sJ-Ls; Thu, 26 Apr 2012 12:13:44 -0500
Message-ID: <4F998214.8030606@jesup.org>
Date: Thu, 26 Apr 2012 13:12:52 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Nicholas Weaver <nweaver@icsi.berkeley.edu>
References: <4F840709.4020103@alvestrand.no> <CAEdus3+Muyy73UoXYuNv6K3OqaSnUYkZh5yBYcpOT1M4oqBc3w@mail.gmail.com> <4F87EF2B.1010805@jesup.org> <201204201355.36264.mirja.kuehlewind@ikr.uni-stuttgart.de> <4F91772F.8010806@jesup.org> <791AD3077F94194BB2BDD13565B6295D2509B178@Polydeuces.office.hd> <4F958A16.6070505@jesup.org> <791AD3077F94194BB2BDD13565B6295D2509C952@Polydeuces.office.hd> <4F95D01B.1020003@jesup.org> <791AD3077F94194BB2BDD13565B6295D2509E0F0@Polydeuces.office.hd> <4F9722D5.2020105@jesup.org> <791AD3077F94194BB2BDD13565B6295D2509FE9A@Polydeuces.office.hd> <2CB80A7D-2F91-4576-8116-FF171EB82E2C@icsi.berkeley.edu>
In-Reply-To: <2CB80A7D-2F91-4576-8116-FF171EB82E2C@icsi.berkeley.edu>
Content-Type: multipart/alternative; boundary="------------050300070706010303050807"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: "ledbat@ietf.org" <ledbat@ietf.org>, "rtp-congestion@alvestrand.no" <rtp-congestion@alvestrand.no>
Subject: Re: [ledbat] [R-C] LEDBAT vs RTCWeb
X-BeenThere: ledbat@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mailing list of the LEDBAT WG <ledbat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ledbat>, <mailto:ledbat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ledbat>
List-Post: <mailto:ledbat@ietf.org>
List-Help: <mailto:ledbat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ledbat>, <mailto:ledbat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Apr 2012 17:13:59 -0000
On 4/26/2012 11:49 AM, Nicholas Weaver wrote: > On Apr 26, 2012, at 8:05 AM, Rolf Winter wrote: >>> http://www.infres.enst.fr/~drossi/DATA/PRJ-Ledbat+AQM.pdf >>> >>> It seems like AQM causes LEDBAT to promote to behavior similar to TCP, >>> but with low delay. Since it still seems fair, this is ok, but it's no >>> longer a background or scavenger flow, and applications using it need >>> to be aware they can impact "foreground" flows if AQM is in play. >>> Perhaps applications need to be given awareness when LEDBAT detects >>> active AQM (if it can), and there's no "scavenger" CC algorithm for AQM >>> that I know of. >> And the document makes that clear and I am not sure LEDBAT actually can detect AQM. > One thought: Active Queue management will be either ECN or early drop. Which is a signal separate to the delay signal used which is "friendlier than TCP". > > In either case, the scavenger flow property might be, well, not fully maintained but at least encouraged by backing off more than conventional TCP would to the same signal. Correct, and that's a reasonable way to proceed - though it might complicate slightly (and certainly change) the LEDBAT competing with LEDBAT case. In my delay-sensitive CC algorithm, I detected drops, and in particular "fishy" drops where the end-to-end delay in the following packet was lower by roughly the normal arrival interval, and would take those as an indication that we should drop more substantially than 'normal'. This was targeted at tail-drop detection, especially congestion spikes, but for a scavenger protocol the same idea could apply to make it more responsive to AQM. Basically, for a scavenger protocol any drop is a warning that either you or someone else has pushed a queue up to tail-drop levels, or that AQM is in play. In either case you should back off, and if you back off more than TCP would, that that allows TCP to retain it's foreground advantage while not hurting scavenger performance (much?) when it competes with itself. It may want to use drops to develop an estimate of the bottleneck queue depth (if less than the target value), to help avoid triggering tail-drops when not competing with TCP. (I.e. a target of 100ms doesn't make sense if the bottleneck queue is 50ms deep - and you can consider AQM really the equivalent of a minimal-depth queue at the bottleneck.) Such an estimate (which would be near 0 for AQM) might let it properly handle AQM, which is an idea which might help in RRTCC as well. For those looking for the "RRTCC" (horrible name :-) draft, here's the latest: http://tools.ietf.org/html/draft-alvestrand-rtcweb-congestion-02 From: harald@alvestrand.no This is mainly a maintenance update. No changes to the algorithm, but reworded to show how it can be applied across multiple SSRCs at one time. Harald -------- Original Message -------- Subject: New Version Notification for draft-alvestrand-rtcweb-congestion-02.txt Date: Wed, 25 Apr 2012 05:03:35 -0700 From: internet-drafts@ietf.org To: harald@alvestrand.no CC: holmer@google.com A new version of I-D, draft-alvestrand-rtcweb-congestion-02.txt has been successfully submitted by Harald Alvestrand and posted to the IETF repository. Filename: draft-alvestrand-rtcweb-congestion Revision: 02 Title: A Google Congestion Control Algorithm for Real-Time Communication on the World Wide Web Creation date: 2012-04-25 WG ID: Individual Submission Number of pages: 17 Abstract: This document describes two methods of congestion control when using real-time communications on the World Wide Web (RTCWEB); one sender- based and one receiver-based. It is published to aid the discussion on mandatory-to-implement flow control for RTCWEB applications; initial discussion is expected in the RTCWEB WG's mailing list. -- Randell Jesup randell-ietf@jesup.org
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Randell Jesup
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Mirja Kuehlewind
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Michael Welzl
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Michael Welzl
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Randell Jesup
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Rolf Winter
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Randell Jesup
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Woundy, Richard
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Rolf Winter
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Randell Jesup
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Rolf Winter
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Randell Jesup
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Randell Jesup
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Rolf Winter
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Nicholas Weaver
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Randell Jesup
- Re: [ledbat] [R-C] LEDBAT vs RTCWeb Randell Jesup