Re: [iccrg] LEDBAT++, rLEDBAT, and slowdowns

marcelo bagnulo braun <marcelo@it.uc3m.es> Mon, 09 September 2019 10:01 UTC

Return-Path: <marcelo@it.uc3m.es>
X-Original-To: iccrg@ietfa.amsl.com
Delivered-To: iccrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFAF512004C for <iccrg@ietfa.amsl.com>; Mon, 9 Sep 2019 03:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=it.uc3m.es
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 mrvrz-kY233t for <iccrg@ietfa.amsl.com>; Mon, 9 Sep 2019 03:01:37 -0700 (PDT)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BAB3120043 for <iccrg@irtf.org>; Mon, 9 Sep 2019 03:01:37 -0700 (PDT)
Received: by mail-wm1-x336.google.com with SMTP id g207so13060589wmg.5 for <iccrg@irtf.org>; Mon, 09 Sep 2019 03:01:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it.uc3m.es; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=1KKOkEW34hrt2GMR9ycv51uD6LLrpfPKq8/zV1xHRVA=; b=RFI4tlLRpp14OYjDK0nD4gcQUjRQY3A1ciNo09Xf5u42gUFf/EwvI86cgxHUll5j/X taUCeQEkglZo7eaIvwG8vB0KahXthNMBbmP5660iQAtZSO+gJiUBQdDZTpgzvnRijQun xx/gR0qPiItDwzDJuDtbQvnZqt72dyNf/DT0rv/HdB/9hOYlQHq7G2QSH67F95BqjEqn PB4Z3oGzbydMkGezEoIBuISO/JoWLdcat532M45XPmeh6bs9XDvAnqs/f++aUVJAxwO7 Gv99t6y+tMixFZTxkDhotoQahrrrRQ9xD58EfPfD8yQ5ovFOgapnZ3qcbGbq1b1ApI5Y hA+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=1KKOkEW34hrt2GMR9ycv51uD6LLrpfPKq8/zV1xHRVA=; b=A1ac9EqsI33yJgWdYkGl1JaXIednRCxDtPgBqOnV19MTPncdY036JHFO83YxYm5UMX JYrwqlpEWmLdeciudtXsv1dIRcW2C8v7ao8Fvwa8/KROiSZRDziGkt8uK6BnFTbT7Z7s XmGvVYqAJPly/Gd80FYnewzFQa5QSmQl8GPsJ2CUIqAAbf4uaW+e26JcPjauMbRVhLNq xs725REfM15j+8o215enyWQb8SAy/JAt0PYNKkVv0j57sr1o9Mqj9et2RAg/3weeY2mS r6vPSROMEc6VkPOf1rRWWwCAiqF95pdbzMhrAW2Uq6oh22cPqnHztoAvQxIDJcTcVcz8 F7Mw==
X-Gm-Message-State: APjAAAXX3JgnrKrqNQ5LEnUOvLUSb4o+EkVW+wrU3aVQE7yTX806GJ80 YRHHcs+krpJtROBhpSrtFtBUPw==
X-Google-Smtp-Source: APXvYqyvClDv0wFo8hyrZbDYOEIKlufaaGSe0Q9fED58mBAZBGNnLjx1yU+/smeJ7hnv74d6msdR8g==
X-Received: by 2002:a1c:a697:: with SMTP id p145mr16347471wme.24.1568023295983; Mon, 09 Sep 2019 03:01:35 -0700 (PDT)
Received: from Macintosh-6.local ([163.117.139.228]) by smtp.gmail.com with ESMTPSA id o8sm11280634wmc.30.2019.09.09.03.01.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Sep 2019 03:01:35 -0700 (PDT)
To: Neal Cardwell <ncardwell@google.com>
Cc: iccrg IRTF list <iccrg@irtf.org>, Praveen Balasubramanian <pravb@microsoft.com>, Yuchung Cheng <ycheng@google.com>
References: <CADVnQynJY8xkqkghhCWhPpbF+4Ev_3c7OZf_tDEb_J5xr0FV9A@mail.gmail.com> <c4b76af5-abbe-3184-24ce-03a2c0b9544b@it.uc3m.es> <CADVnQy=3FqEjqipX6thgjcjN8YPTOqiduYKU2GccXHwS+a3wVA@mail.gmail.com> <be98e323-506f-bdc8-a128-72c9f4aa5ead@it.uc3m.es> <CADVnQykxubLk-o02im1T-Xd_6BT=TT6nSSYfP2MDPFO5hAorfA@mail.gmail.com>
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Message-ID: <2f779633-f8d6-3af4-78b0-b968e8f47ac5@it.uc3m.es>
Date: Mon, 09 Sep 2019 12:01:34 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CADVnQykxubLk-o02im1T-Xd_6BT=TT6nSSYfP2MDPFO5hAorfA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/iccrg/FeQL70sb2fwurlTDozGb8Gb_dYo>
Subject: Re: [iccrg] LEDBAT++, rLEDBAT, and slowdowns
X-BeenThere: iccrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussions of Internet Congestion Control Research Group \(ICCRG\)" <iccrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/iccrg>, <mailto:iccrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iccrg/>
List-Post: <mailto:iccrg@irtf.org>
List-Help: <mailto:iccrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/iccrg>, <mailto:iccrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2019 10:01:40 -0000

below...

El 06/09/19 a las 17:02, Neal Cardwell escribió:
>
> Yes, rather than synchronizing using losses, I had something in mind along
> the lines I proposed earlier in this thread; something like
> BBR's PROBE_RTT mechanism:
>
>     ... the
>     only approach I can think of to achieve this would be for the flows to
>     coordinate in some fashion to all do a slowdown during overlapping
>     time intervals (as in BBR's PROBE_RTT mechanism).
>
> The details of BBR's PROBE_RTT mechanism are described in:
>    https://tools.ietf.org/html/draft-cardwell-iccrg-bbr-congestion-control-00#section-4.3.5


Thanks for the pointer. So, if i understand this correctly, essentially 
the proposed mechanism is that the flow slows down 10 seconds after the 
last update in the estimation of the base delay.

Is this it or am i missing something?

I understand that the expectation is that if there are several flows, 
the slow down of one them will cause the update of the base delay of 
several flows. These flows are now synchronized, so when they all slow 
down at the same time, they will cause even more flows to update their 
base delay estimation, and eventually all of them will be synchronized 
in their slow downs and then properly assess the base delay.

If this is so, I guess one question is how to know for sure that when 
they are in the uncoordinated state, the slow down of one of them will 
cause the update of the base delay of other flows, no?

Thanks, marcelo




> best,
> neal
> .
>