Re: [iccrg] Background on my talk in iccrg

Bob Briscoe <ietf@bobbriscoe.net> Wed, 03 April 2019 10:48 UTC

Return-Path: <ietf@bobbriscoe.net>
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 95080120091 for <iccrg@ietfa.amsl.com>; Wed, 3 Apr 2019 03:48:09 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=bobbriscoe.net
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 3cunnrhExr0S for <iccrg@ietfa.amsl.com>; Wed, 3 Apr 2019 03:48:06 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1E571200B5 for <iccrg@irtf.org>; Wed, 3 Apr 2019 03:48:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:References:To:From:Subject:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=S2nJa5HvJ+phXmu3ZxKt896fgkepioEA2/TfisuiDNU=; b=8ikyoMAxU9k9/8jkV6/Tf/tYr nBl169yK+PXiD+HTdxKSyRPDvgdUeAHQypWPCboBryoyomNqDGzmUsPZr6YtCIDmJoBIa3WsP5xDR 20tyOVKgrWueliujFgqxg5O/wiFhaOrcR7Z3eVy8fIfdkRmNI3GAnPpQj4LU6YKjTm9TaU+frzrbw FPC0X30w04TtBxfkTaQoCuIqVVcVNNISsCuO8P2TWc/tpZE471JclUUIpqmg47HUluIhKB8Qb0JJw 82KSMjPk0rxH/HRtpgykhV/d9UeeE84hQLLelWG7Rin8WQ91WPAJAk8e+uVNiALbX4YhyjS525DCK EmDZemvDA==;
Received: from [31.185.128.56] (port=54976 helo=[192.168.0.7]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <ietf@bobbriscoe.net>) id 1hBdR5-0002tc-Br; Wed, 03 Apr 2019 11:48:03 +0100
From: Bob Briscoe <ietf@bobbriscoe.net>
To: Peyman Teymoori <peymant@ifi.uio.no>, "iccrg@irtf.org" <iccrg@irtf.org>
References: <9D7CBDDC-EEDC-4510-96D6-EA893826F190@ifi.uio.no> <d05eb4b8-53ae-82be-5442-711c3316940b@bobbriscoe.net> <9be2b58a-4664-c2bd-378d-38feeea193e8@bobbriscoe.net>
Message-ID: <fc81e540-3f81-d6c7-bbdc-2fd2d03774e6@bobbriscoe.net>
Date: Wed, 03 Apr 2019 11:48:02 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <9be2b58a-4664-c2bd-378d-38feeea193e8@bobbriscoe.net>
Content-Type: multipart/alternative; boundary="------------D9A32698749D904380BE8321"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/iccrg/rvH4Pxa_zE7ys8XnnBy3ziOHrpA>
Subject: Re: [iccrg] Background on my talk in iccrg
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: Wed, 03 Apr 2019 10:48:10 -0000

Peyman,

1/ I realize now that I incorrectly appeared to be dismissing your work 
in my email and my comment at the mic. I apologize.
Your -log(1-p) formulation does indeed have the correct additive 
property. Thank you for this.

2/ Implementation
You say "...we will consider deployment challenges more thoroughly in 
our future work." Surely this is a sender-only algorithm, so there is no 
deployment challenge? However, there is a (minor) implementation 
challenge. Perhaps that's what you meant?...

2a/ With the current DCTCP approach of updating an EWMA of the 
congestion level once per RTT, I don't think implementation will present 
too much of a performance hit.

(1-p) could be calculated by maintaining counters of the number of 
unmarked bytes and total bytes, then every RTT using an efficient 
integer division, such as do_div() in Linux, then using an efficient log 
implementation. I'm not sure what to do when there's 100% marking to 
avoid calculating -log(0) = +infinity. Aside from that issue, I don't 
think this calculation would harm performance too much, although I would 
prefer not to have a regular spike of processing time...

2b/ We liked p/(1-p) because it lends itself to a simple iterative 
calculation on every ACK or NACK. That's because there are (1-p)*cwnd 
ACKs per round trip and p*cwnd NACKs per round trip. So an increase can 
be applied on each ACK and a decrease on each NACK.

This insight was not our idea - I first saw it in Richard Gibbens's and 
Peter Key's tutorial "Distributed Control and Resource Pricing" at 
SIGCOMM 2000. They used it when modelling TCP's AIMD.

I much prefer iterative algorithms, cos they are stateless. Otherwise 
TCP gets more and more complicated with all the possible combinations of 
modes you have to allow for.

I can't think of a way to iteratively calculate -log(1-p). I've only 
tried for a few minutes, but I can't really fathom where to even start. 
I also cannot think of a good way to reason about what base should be 
used for the log.

-log(1-p) and p/(1-p) have similar shapes, so maybe the latter would be 
a suitable approximation for the former anyway. Normally I criticize 
others for developing solutions without any theoretical backing just 
because they are easy to implement. Now I'm guilty of it myself. I'm 
much happier now we can start from your theoretical ideal, then 
approximate it for ease of implementation.

Thanks again,



Bob

On 28/03/2019 16:56, Bob Briscoe wrote:
> Addendum...
>
> On 28/03/2019 17:03, Bob Briscoe wrote:
>> Peyman,
>>
>> The approx additive property of combinatorial probability at low 
>> marking probability is only one way to get the additive network 
>> utility maximization property of the network.
>>
>> Alternatively, you can transform the signal into the number space 
>> between [0,1] by using p/(1-p) which you can do in the end-system by 
>> measuring your congestion level as the distance between ECN marks, 
>> rather than the the probability of marking.
>>
>> This is explained in the Unsaturated Marking section of this tech report:
>> http://bobbriscoe.net/projects/latency/ccdi_tr.pdf#subsection.3.1
>>
>> We presented some of the highlights of this paper in ICCRG in the 
>> past, but I think we had to skip this section, due to lack of time 
>> (at least I cannot find the slides we originally prepared in the copy 
>> in the IETF proceedings, but I thought we had presented it at some time).
> [BB] I just found it:
> http://bobbriscoe.net/presents/1703ietf/1703L4S_DualQ_TCP_Prague-iccrg.pdf
>
>
>
> Bob
>>
>>
>> Bob
>>
>> On 21/03/2019 13:18, Peyman Teymoori wrote:
>>> Dear all,
>>>
>>> I would like to share the report (preprint) we have been working on with you before the meeting in Prague since my presentation will be about it. This is actually a research work, and we will consider deployment challenges more thoroughly in our future work.
>>>
>>> Kind regards,
>>> Peyman
>>>
>>>
>>> _______________________________________________
>>> iccrg mailing list
>>> iccrg@irtf.org
>>> https://www.irtf.org/mailman/listinfo/iccrg
>>
>> -- 
>> ________________________________________________________________
>> Bob Briscoehttp://bobbriscoe.net/
>
> -- 
> ________________________________________________________________
> Bob Briscoehttp://bobbriscoe.net/

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/