Re: [rmcat] delay recovery phase

John Leslie <john@jlc.net> Mon, 03 November 2014 15:33 UTC

Return-Path: <john@jlc.net>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE2F31A02F1 for <rmcat@ietfa.amsl.com>; Mon, 3 Nov 2014 07:33:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.794
X-Spam-Level:
X-Spam-Status: No, score=-4.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594] 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 njdPFTQfwqTD for <rmcat@ietfa.amsl.com>; Mon, 3 Nov 2014 07:33:03 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 2E8561A0211 for <rmcat@ietf.org>; Mon, 3 Nov 2014 07:33:03 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id D6D27C94C8; Mon, 3 Nov 2014 10:33:00 -0500 (EST)
Date: Mon, 03 Nov 2014 10:33:00 -0500
From: John Leslie <john@jlc.net>
To: Stefan Holmer <stefan@webrtc.org>
Message-ID: <20141103153300.GP525@verdi>
References: <479bbc3c4afe41cc8c8226c71a96de2c@NASANEXM01E.na.qualcomm.com> <54552241.2080400@jesup.org> <CAEdus3+XMFPZH7kyUscg5xQJoWE8ywcDFVaPzyemT474mXGYMQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAEdus3+XMFPZH7kyUscg5xQJoWE8ywcDFVaPzyemT474mXGYMQ@mail.gmail.com>
User-Agent: Mutt/1.4.1i
Archived-At: http://mailarchive.ietf.org/arch/msg/rmcat/YHgDkHJ1SlFxEwTCtY3Y2TAW_Vw
Cc: rmcat@ietf.org
Subject: Re: [rmcat] delay recovery phase
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Nov 2014 15:33:04 -0000

Stefan Holmer <stefan@webrtc.org> wrote:
> 
> In https://tools.ietf.org/html/draft-alvestrand-rmcat-congestion-02#page-10
> we go into a HOLD state where the sender should keep its bitrate constant
> while waiting for buffers to drain.

   The first time I read this, I thought you were saying to hold the rate
constant regardless of what was happening to the delay.

   I think it would be good to explicitly state something to the effect
that rmcat will have a target delay, and will not increase sending rate
until that target is achieved.

   (Of course, that target may change if it turns out to not be
achievable...)

> We don't try to estimate the time needed to drain the buffers, but
> instead look at the delay change estimate m(i); if it's less than zero
> buffers are likely draining.

   There must be a better way of saying this...

   We can only track the delay (including rate-of-change): IMHO it's
better not to talk in terms of buffers draining, merely delay.

   (Isn't that the actual goal of rmcat -- to achieve low-enough delay?)

--
John Leslie <john@jlc.net>