Re: [Lsr] Zaheduzzaman Sarker's Discuss on draft-ietf-lsr-isis-fast-flooding-08: (with DISCUSS and COMMENT)

John Scudder <jgs@juniper.net> Fri, 05 April 2024 11:46 UTC

Return-Path: <jgs@juniper.net>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4188C14F6B1; Fri, 5 Apr 2024 04:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level:
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.08, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net header.b="kD5zMsPg"; dkim=pass (1024-bit key) header.d=juniper.net header.b="CoZu/X2v"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q_nm4vFl77yQ; Fri, 5 Apr 2024 04:46:18 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 F163BC15107A; Fri, 5 Apr 2024 04:46:17 -0700 (PDT)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.17.1.24/8.17.1.24) with ESMTP id 4359i14u028414; Fri, 5 Apr 2024 04:46:15 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h= from:to:cc:subject:date:message-id:references:in-reply-to :content-type:mime-version; s=PPS1017; bh=5npy4FbxrUYEG4IIayugnP R3DcT5+Wp+rMebNrL4LiI=; b=kD5zMsPg8j7hq1OJmbajp1uNSbH5m3rFFIIDUI cc1p9PDmBt6uosS6ujPCGgtr1NGt007Nt6z0VLp7rmSz/LqGcOX6t3I5V1EwHP0I ctnblGsHG9LyZ2W7JGF+Xo8P71WqwGZEzCq6nTXUmjUcezKuhIV0BGRipuz0vKKl LNx7DQJqJGDXYXngsd24taByzLDvGDdpX+8ZFlwmAHUHs40S7OF4Jlib6ZPQePTR LKEduFK62TleO7hKB5Tw6J7ky+z1M7/U09qggcIa5wfLjnIFduhD7Mllx7gc/iTy bnap/S8j4mjPHSRq9j+bTvJflhc2YVQihsJ8CRFolN9+6ORQ==
Received: from cy4pr05cu001.outbound.protection.outlook.com (mail-westcentralusazlp17010009.outbound.protection.outlook.com [40.93.6.9]) by mx0a-00273201.pphosted.com (PPS) with ESMTPS id 3x9epa3rmm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 05 Apr 2024 04:46:15 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eFnncbHXCtVpuvTTa43FoU4ptkgTXmXwmCZbQF5PYdmQWoORH6xbjEN0kH/DipcY5obr4Xkp6adDcAd8ZDCrpy8VdAfqF/NoqX4UQwHJ5AVp1ZShS5TjLL11VAS2W+LAB8izGh1MMz51y27Ft7nQhLOdfHuHBr7lBmF9cZYPxYJw+9aY30pbPBWmpt/fNF/Kaubvhzf40BbC4H2l9sh+nkWsuE2OA1ozgAftp7rKUlLQuvX6EDlEJ5ONhFSppg0Pn6OvNu7IMrHZTKhVrSTq27GXsR/3ayku6dNNlStj4lM/hKPZdb6Q3AgsWIQKjzwDo7KTBG+Ddn2p5uFf72d5+g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=5npy4FbxrUYEG4IIayugnPR3DcT5+Wp+rMebNrL4LiI=; b=TwWbMd0FTRPRzfB2lac4rM0do86mBG4w94o9vJ0XeWG5POMgN9GcU5hRjnsC6DsUcEJ7xDhR1My37dKRURID46FU5LvxKK261NVXJQNmBcbr4uxCFahUZztIKgVPWhoO/9SNbw0Afycj17ehA5XYI2NI0FIcXh0x4RflmYeNH06Zs63Kc8XLKNjcdP0iRgcLc+wqWcbX8AteYixIsGklNQ2Mn/RSPaxmTPOGdUflwSxGBn374tZ3eI7763Ixq2cyG9JDBnvRCw7Gc356h5vosA/UCWRqgpLPD7Vgh2zVhPrdTRbQuOynJibnzm/XUKmxiTAju8iM+YjzGQyfUX7iwA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5npy4FbxrUYEG4IIayugnPR3DcT5+Wp+rMebNrL4LiI=; b=CoZu/X2vNQKNKCFjOD9+7VGoC0aXa4hxFdP/qTopds92H2w6FmrcA2TFOfdAGp8rzlWFCH6zTa3YcFy/JCgtG7Yb/b0bxXiyy2aWlq/sWP3s6beA8sD4v68vXgmm0toI4ZTtLEtvCY3BUhqn7uun01BaIHjOvq2ixyBNGDZag+s=
Received: from CH2PR05MB6856.namprd05.prod.outlook.com (2603:10b6:610:3e::11) by CY5PR05MB9071.namprd05.prod.outlook.com (2603:10b6:930:3d::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7409.40; Fri, 5 Apr 2024 11:46:12 +0000
Received: from CH2PR05MB6856.namprd05.prod.outlook.com ([fe80::f1bf:41e0:23ff:7eff]) by CH2PR05MB6856.namprd05.prod.outlook.com ([fe80::f1bf:41e0:23ff:7eff%5]) with mapi id 15.20.7409.042; Fri, 5 Apr 2024 11:46:11 +0000
From: John Scudder <jgs@juniper.net>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
CC: The IESG <iesg@ietf.org>, "draft-ietf-lsr-isis-fast-flooding@ietf.org" <draft-ietf-lsr-isis-fast-flooding@ietf.org>, "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, "acee.ietf@gmail.com" <acee.ietf@gmail.com>, "acee-ietf@gmail.com" <acee-ietf@gmail.com>
Thread-Topic: Zaheduzzaman Sarker's Discuss on draft-ietf-lsr-isis-fast-flooding-08: (with DISCUSS and COMMENT)
Thread-Index: AQHahnktC9cHLzAkGUWWIjh/x/cHw7FYI5yAgADv2wCAAH1NTQ==
Date: Fri, 05 Apr 2024 11:46:11 +0000
Message-ID: <5EF26B4C-6C5E-461D-87D8-933706D4BF4C@juniper.net>
References: <171222579232.2606.7357707210840921573@ietfa.amsl.com> <98758CCB-5E9D-4F69-9F50-E6BCD6329746@juniper.net> <BY5PR11MB43372062BD7A234A7D88824DC1032@BY5PR11MB4337.namprd11.prod.outlook.com>
In-Reply-To: <BY5PR11MB43372062BD7A234A7D88824DC1032@BY5PR11MB4337.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: CH2PR05MB6856:EE_|CY5PR05MB9071:EE_
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: vMPKyNeag/Wbcg1/tIEWcXa/e/t923cxeAniupByXnEu3YD3Qik3lnc4pOgyFcUpQjOsP8NTGPf8g3+WG3TjCbKRHF2w3DPaYAGErzv9q6CNATpJdgdX0/nQy0Nw+4jkQ4dhEVsvkJY4/24iIn1SokX4XiA0wQJaQOxG+OCSGPspdCMm+oDRfnTazuWNfHIUAtQbe0s+DxNr9/SRcFJlG1w6WqimEqHH1mqWycK96fsAQw36yJ4ZQQTGBRxvr0wYo/QUjUNRfpeXydrHLLOVpKXfW1A6LJcQP6JrWQ/hO7Yma9pot28urCDP9S5JFn+YwrkmhNILQuHjQLq2/lgfN9SwpMvGxu1cWrKSchPQtKCT3UgHWYRqX5eaZu7ikJKCN/nqESHgS8RU92bputN7lbPEikC+5ZetVoGyYYqNHKdxl5dqskQ+pRE9fwDg47bQy7Ks5W0HRxVLnB6NB+1/FvjpWS38gLOI6bbL5g0eJ9GKT0+pbWWWY5n0NTHSrDXYrEVwjc3h/2rBhUN53IWuH6ASs2/mJrXEiG+OWt9WHqbPLLuZzpBS8gjBfeBrYMvDLJKL7f+/jPpsnbTMsp/KDbeRMdlNUi/Js1hOmmveqBg=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CH2PR05MB6856.namprd05.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230031)(376005)(1800799015)(366007); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: tmG+B3BDQAtep2UDIsjWMoRyL+fhPIyyDvFKi+s/TCc7ielPYpLaombfYKvisrFAdl3TBAhOsINBWcyNDP9/ikKVwnH9MPn/91G+7g2nUXreKC5B5yaBs9J1ShTE6vId7djdHPW8jIZ2aMEnqbnU4DgVSjpO1B4S0yLN4cIdYxoBXqdrycjSc/cDA9+KInuUVOh+eYVSmsmQfJdhhiGPe1u29oBdjwZ1c2oxYORrc9WaoLXea0P3W6cY0VWXRSb73jeFdVYrw3UCUS+afGPEUjCBlHaxgTSh8+vtuhvmvadMPbOeSJGmQlueOTjuILpIlBB2DmpDmeSwFgowfF34H+2m8Oy7yitvw6R7aIEsOlb5/f10M1/3PD8tQ0XQe1hyc+jgDAly4PwvF6t3gHHQVX0C2uvqn4NFgiAj3L7kfUylu3xUhW0bd0b4EqZQH1stJjtr0ORx23swQ4f/jAbS89GMmirspIeY5AKL1JJfmnHEBenOfLWpLRbFqF13kwD+Lssu/nfHA3d7Nh5ly40998f5cT+FP9zIB5FmBaLfyGTu8vplIwar18UwF+sgp2NEd15fuB9fGtraGlg7C36iWR3JB1bmZN6MPFf1CYYUNEpNiS1mhCCUDrgr7t96l19WeoRLGJ3+p3WBtcL8GCSD16UGNNcRf6zg564AsYpBDbWMTmVAH/pD2DK1FjomnvMgpmeDIF5Ldk8UbRR1qfFxoMW5mpglrTG4PNnGDKwPwam5e5jW58olfx32VTzN44ALDtluxbvJsE2ZljfkGGKET3UXjRVJ3qTCvuweq2+/gFCR7mIQ0yJZp+K9R6FoI8GhYI9v8yyPmB4CVod457fj659aVmcUHceS4MTLHOxZaLfxSvPjRuMq7EcTf/N+wy9WwOMsR2TIVs0SJCtIpRJyJMvLjETgAVgyvG/pnuyAOLQX5AVvoBEDLUhIRPPcdQUkjSjUqsbxoET58KLLwp6Z+Oxf3hDKdptwopjKvdWbmtGuVTGMFHpyFXHzzdJv6mVn7KIp7QUHWCcO7O4I+nHh4CD8szwLrH8YUGiroVnxddNT6+w8aLJSP10HGTx5WOtbsf8gzGRttpvkpZdBvA0oywBVLP+xyhpz+qP7lxNAMkrNlWl/u3iwmAf/jcHnElqltmHCrun8geCuNo01lfMhBgQeQceYYg6nCe31bGTNlxqXJV2yJllMM4BfxPm9N7r62rqyT17Cafg4I0w6Ee14XSH67qnYn7cNK7BdQ5Pczy2HY6eS5Dt++SrcyMCKXgcc7l8VSAPrvSj7tvt6ZDY2/VfHrF00yuyjK1uzZW0U9ggMeUsCvmSZ7UktouK2OyyVaLt+mukI5a1MvfgyFcYGo1GPKtWxrpR1UdGqGVE1p6Vdq+FVyLVObIeEK/6ag8BBjk7Tr/xPbt2nrOETGkCqMFIOep/wzbxmMPAktaHhA/FMxTZYsxxAB6DLHclAzT5G/Dx7M5aFVk552CUlnbgSxUh2lv3UdGQAVqGJlEi4yn0wc6nq4mnmqOZh/wlakQJ7rbu4UvcQtf/d9EvgDsURhgFUsfybr6de1wfljgl5oFjXwd7hxT0FcapqX6BvqUVj
Content-Type: multipart/alternative; boundary="_000_5EF26B4C6C5E461D87D8933706D4BF4Cjunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR05MB6856.namprd05.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a5400735-2cbc-446f-467b-08dc5565fdd0
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Apr 2024 11:46:11.8058 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: cQh9t/45RFoo9HFT6FAVLuRWkQuW+H957udL1mm2avikkyVpBx5GJzvrDkiBTHVo
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY5PR05MB9071
X-Proofpoint-ORIG-GUID: hiXRwU1ZRQNTmEJTmtNUfbRB2qOyIER0
X-Proofpoint-GUID: hiXRwU1ZRQNTmEJTmtNUfbRB2qOyIER0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1011,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2024-04-05_10,2024-04-04_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 clxscore=1011 spamscore=0 adultscore=0 priorityscore=1501 mlxscore=0 malwarescore=0 suspectscore=0 impostorscore=0 lowpriorityscore=0 mlxlogscore=999 phishscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2404010003 definitions=main-2404050084
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/NHd9x6rtWp9iCwMLnqFqis_1hIk>
Subject: Re: [Lsr] Zaheduzzaman Sarker's Discuss on draft-ietf-lsr-isis-fast-flooding-08: (with DISCUSS and COMMENT)
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2024 11:46:21 -0000

Adding Zahed’s current email and deleting his old/nonfunctional one.

— John

On Apr 5, 2024, at 12:17 AM, Les Ginsberg (ginsberg) <ginsberg@cisco.com> wrote:



[External Email. Be cautious of content]

John/Zahed –

In regards to Algorithm 2, note that older versions used the term “Flow Control”, but based on the discussion with Mirja (not that I am blaming her…) we changed that section to use the term “Congestion Control”.

This seems proper to me. If one looks at Section 6.1 – and in particular paragraphs 2 and 3 – congestion control seems like the correct choice.


Zahed – I would appreciate your updated response after rereading those paragraphs.

John – I am not entirely clear on what would address your comment. Would replacing “algorithm” with “approach” in Section 6.3.2 be satisfactory?

  Les


From: John Scudder <jgs@juniper.net>
Sent: Thursday, April 4, 2024 6:59 AM
To: Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>
Cc: The IESG <iesg@ietf.org>; draft-ietf-lsr-isis-fast-flooding@ietf.org; lsr-chairs@ietf.org; lsr@ietf.org; acee.ietf@gmail.com; acee-ietf@gmail.com
Subject: Re: Zaheduzzaman Sarker's Discuss on draft-ietf-lsr-isis-fast-flooding-08: (with DISCUSS and COMMENT)

Hi Zahed,

I guess the authors should respond comprehensively. I do have one response to your comments on algorithm 2, though. They seem to boil down to your first comment, "Can we really call congestion control algorithm 2 a congestion control algorithm?” It seems to me, on looking at the document again, that the answer is probably “no”. From §6.3.2, with emphasis added:

"When congestion control is necessary, it can be implemented based on knowledge of the current flooding rate and the current acknowledgement rate. **Such an algorithm is a local matter and there is no requirement or intent to standardize an algorithm.** There are a number of aspects which serve as guidelines which can be described."

I wonder if it’s both necessary and sufficient to reword “algorithm” 2 to be called something else, and to remove the RFC 2119 keywords from 6.3.x. As I read the quoted text, it’s not an algorithm, it’s hints towards an algorithm.

Looking forward to your comments and those of the authors.

—John


On Apr 4, 2024, at 6:16 AM, Zaheduzzaman Sarker via Datatracker <noreply@ietf.org<mailto:noreply@ietf.org>> wrote:

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-lsr-isis-fast-flooding-08: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://urldefense.com/v3/__https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!NEt6yMaO-gk!C4IK0qxrHCShIaZBQk48oNHSXQ7rb3GAhaymBNFbvj-okuR1iO8UDVkcxrsY1Kxfqj_vVLgd108E$<https://urldefense.com/v3/__https:/www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!NEt6yMaO-gk!C4IK0qxrHCShIaZBQk48oNHSXQ7rb3GAhaymBNFbvj-okuR1iO8UDVkcxrsY1Kxfqj_vVLgd108E$>
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-lsr-isis-fast-flooding/__;!!NEt6yMaO-gk!C4IK0qxrHCShIaZBQk48oNHSXQ7rb3GAhaymBNFbvj-okuR1iO8UDVkcxrsY1Kxfqj_vVG87RLDF$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-lsr-isis-fast-flooding/__;!!NEt6yMaO-gk!C4IK0qxrHCShIaZBQk48oNHSXQ7rb3GAhaymBNFbvj-okuR1iO8UDVkcxrsY1Kxfqj_vVG87RLDF$>



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks for working on this specification. Thanks for Mirja for the TSVART
review.

I would like to discuss the following points as I believe some clarifications
would help -

- Does the flow and congestion control algorithm 1 assume that there is only on
(input)queue in a particular link? I understand that the motivation for
congestion control algorithm 2 is that there are multiple input queues and
defining rwin is difficult. Why is that easy for the case of algorithm 1?

- Can we really call congestion control algorithm 2 a congestion control
algorithm? We are are really solving the problem of flow control, it sounded
more like a emergency break ( aka circuit breaker ) to me where you reduce or
even stop sending LSPs. My point is I am not sure how to interpret the
congestion control algorithm 2 with any sort of details. If I replace section
6.3.2 with - "if the routing architecture does not support deterministic rwin,
the transmitter MUST adapts the transmission rate based on measurement of the
actual rate of acknowledgments received." what harm would it cause?

- For the congestion control algorithm 2, I am missing when the transmitter
should reduce or when it should stop sending as I am not sure reducing the
transmission rate would solve the problem of not. This comes from lack of
details on the particular algorithm that will be implemented eventually.

- Section 6.3.2. says -

   The congestion control algorithm MUST NOT assume the receive performance of
   a neighbor is static, i.e., it MUST handle transient conditions which
   result in a slower or faster receive rate on the part of a neighbor.

 How to separate the persistent congestion from transient slower receive rate?
 I am not sure how to fulfill the "MUST".


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I have some further questions or comments -

- How does the implementers select between congestion control (CC) algorithm 1
and 2? or is the intention that both gets implemented and after experiments we
pick one? As in my discuss point I am not sure about the CC algorithm 2 on how
to conclude on the experiments.

- It already says flow control and congestion control is a Layer-4
responsibility, it would be great if we can say why that is not the preferred
layer for fast flooding even if it may be obvious for some of us.

- Section 6.3.2 says -

   When congestion control is necessary, it can be implemented based on
   knowledge of the current flooding rate and the current acknowledgement rate.

 So, how do we know when the congestion control is necessary?