Re: [Lsr] Congestion (flow) control thoughts.

"Gengxuesong (Geng Xuesong)" <> Thu, 30 April 2020 02:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3A5063A0DB4 for <>; Wed, 29 Apr 2020 19:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.82, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id n82M6cuXOGP7 for <>; Wed, 29 Apr 2020 19:38:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 15B853A0DB3 for <>; Wed, 29 Apr 2020 19:38:26 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id E1C476CB6481A74E89A5 for <>; Thu, 30 Apr 2020 03:38:23 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Thu, 30 Apr 2020 03:38:23 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Thu, 30 Apr 2020 10:38:20 +0800
Received: from ([]) by ([]) with mapi id 15.01.1913.007; Thu, 30 Apr 2020 10:38:20 +0800
From: "Gengxuesong (Geng Xuesong)" <>
To: Christian Hopps <>, "" <>
Thread-Topic: [Lsr] Congestion (flow) control thoughts.
Thread-Index: AQHWHiEz1dI/yoz7M0KHaDn4nVfYx6iQ5nmA
Date: Thu, 30 Apr 2020 02:38:20 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_8016231f9ff94bd2b0f5ef989608922fhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Lsr] Congestion (flow) control thoughts.
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 30 Apr 2020 02:38:28 -0000


Thank you Chris for emphasizing that congestion control is hard and more reference may be necessary.

And as the the follow-up of my comments in the interim meeting, I would like to make my question more clear:

In congestion control of layer 4, it is assumed that there is a bottleneck in the network, and the ideal rate of the transmitters equals to a fair share of the bandwidth in the bottleneck. The flows in the network change all the time and so as to the ideal transmitting rate. There are some methods to detect the bottleneck, for example detecting packet loss, setting ECN, RTT and so on. Considering that the goal of cc is to maximize the throughput and minimize the queuing delay, the throughput and delay could be used to compare different cc algorithms.

The problem of mine is that for CC of ISIS flooding, where is the bottleneck?(maybe the receiver capability) What method of detecting could be used? (In my understanding, we have two options at this stage: one from the receiver side and the other from the transmitter side) What is the criteria of comparing? (still a little confusing for me )

Best Regards


-----Original Message-----

From: Lsr [] On Behalf Of Christian Hopps

Sent: Wednesday, April 29, 2020 8:24 PM



Subject: [Lsr] Congestion (flow) control thoughts.

[As WG member]

I like the start these drafts are making, I have a few thoughts.

- I think its worthwhile work and as a WG we should end up adopting a draft or drafts that try to solve the problem.

- Congestion control is hard, and a very well studied problem, as such whatever we end up should reference prior-art to justify it's claims.

- Data, whatever solution we end up with needs to have data to back up it's claims.

** draft-ginsberg-lsr-isis-flooding-scale

Having just recently offered a, "CC algorithm is local so we aren't specifying it", in some unrelated work, I discovered (correctly so) that it was not sufficient (see [*] for the resulting changes if curious). One needs to provide (doesn't need to be normative) a working algorithm to prove that the protocol is providing enough information to the transmitter to actually implement a viable CC algorithm.

Now draft-ginsberg does suggest an algorithm, however only for P2P. We need to address LAN as well. This also needs references on how this algorithm relates to existing studied work, and perhaps most importantly some data showing that it actually works.

Without this it will almost for sure not clear the IESG (in particular Transport AD review), and rightly so. :)

** draft-decraene-lsr-isis-flooding-speed-03

I read this draft as providing feedback to transmitters on ways to modify the parameters of their CC algorithm. It doesn't actually seem in conflict with draft-ginsberg (or doesn't need to be) to me. I believe it's following the path of least resistance in utilizing existing IS-IS parameters. I wonder if we could be more adventurous here.

** Both

Both drafts mention trying to increase the ACK rate. I think we need to look deeply into this, as this is critical information for CC algorithms. It very well could be that we do not need protocol changes as the protocol provides an ACK (or NACK for LANs), but I also don't think changes or additions should be verboten either if they could provide significant improvements.

In the algorithms we propose or envision we need to be considering the affect of larger RTT on the algorithm for slow or long distant links (radios, satellites, long-haul fibers, etc).



[As WG member]

[*] -,