IETF Logo Mail Archive

Re: Q on the congestion awareness of routing protocols

Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk> Sat, 03 December 2022 12:27 UTC

Return-Path: <Jon.Crowcroft@cl.cam.ac.uk>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDE39C1522A2; Sat, 3 Dec 2022 04:27:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.296
X-Spam-Level:
X-Spam-Status: No, score=-4.296 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_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=cl.cam.ac.uk
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 jXT1Ql0sb3PC; Sat, 3 Dec 2022 04:27:04 -0800 (PST)
Received: from mta1.cl.cam.ac.uk (mta1.cl.cam.ac.uk [128.232.0.57]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81033C1522A6; Sat, 3 Dec 2022 04:27:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cl.cam.ac.uk; s=mta3; h=Message-Id:Date:Content-ID:Content-Type: MIME-Version:References:In-reply-to:Subject:cc:To:From:Sender:Reply-To: Content-Transfer-Encoding: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=x5z/RG0MSV0yUzg2YvGP3DUTB8+60lo1AhSivGb0iL4=; t=1670070422; x=1670934422; b=YWp0oY6aRyiqE32XuPu1DKeq+aMWzoWsGpr2nfvDkjIdnPqBNcBR6myJVcc/BqzcSju4bKqeWh0 aU5Z6XY3KMKIRrWy93Rim0Jai1t5BWAp4xYw4cm/IhnCCfRqbv9nKqSGfOwtLdvSfZY54BBdL8xtl hfcV5Y7uq4b0KXpJf1shV2zcORZmKaK+WR3P5fJU5WL+vRX9oHX3qjKo3D6qPgdJQfqHdOQpdFwCt 25Bxqp0fFsbkupUS1MKXfHYQEcRS//dNtZ6gnx/ndnDlRA5l6L9WiTD1C3v1lRCg3uh9Ih/Ask/L3 Hwcri5XmrqPLHqLcZfeFzdSnREZqZOYm71Qg==;
Received: from svr-ssh-1.cl.cam.ac.uk ([128.232.102.11]:35946) (dnseec=no) by mta1.cl.cam.ac.uk:587 [128.232.0.57] with esmtp (Exim 4.95) id 1p1Rbe-009zgN-1s (envelope-from <Jon.Crowcroft@cl.cam.ac.uk>); Sat, 03 Dec 2022 12:26:58 +0000
From: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>, bier@ietf.org, routing-discussion@ietf.org, tsv-area@ietf.org, pim@ietf.org
Subject: Re: Q on the congestion awareness of routing protocols
In-reply-to: <c86d7ae6-3dad-04be-9c16-0135cc95fe73@necom830.hpcl.titech.ac.jp>
References: <Y4ovyV074qa3gLSu@faui48e.informatik.uni-erlangen.de> <CAEeTejLa8sdJVU_2OfTo=ZgWRY-kv_7M=xiR-bLyBEXhSDP=Eg@mail.gmail.com> <e2527c9c-c7d1-c6b7-a067-e5ccbdc7e997@necom830.hpcl.titech.ac.jp> <E1p1PaX-009tgu-Hl@mta1.cl.cam.ac.uk> <c86d7ae6-3dad-04be-9c16-0135cc95fe73@necom830.hpcl.titech.ac.jp>
Comments: In-reply-to Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> message dated "Sat, 03 Dec 2022 21:20:34 +0900."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3433755.1670070417.1@svr-ssh-1.cl.cam.ac.uk>
Date: Sat, 03 Dec 2022 12:26:58 +0000
Message-Id: <E1p1Rbe-009zgN-1s@mta1.cl.cam.ac.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/8RtPmuaqyAFromWUZzNgLOrvOR0>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-area/>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Dec 2022 12:27:09 -0000

> Jon Crowcroft wrote:
> 
> 
>     i suggest reading
>     https://www.icir.org/floyd/srm.html
> 
> 
> I did so before my previous reply.
> 
> But, it did not affect my understanding that there are so
> many complicated protocols for reliable multicast. As such,
> TCP mesh should be better as long as we follow the CATENET
> model.
> 
> 
>     plus any of many papers on tcp incast
> 
> 
> I'm afraid that if TCP incast is a problem for control traffic,
> there should be no bandwidth left for data traffic.

incast isn't about persistent congestion, it is about synchronised
sources.
> 
> If lack of bandwidth is a problem for data traffic, the way to
> go is QoS routing, which means, over QoS satisfied routes, we
> have enough bandwidth for control traffic.
> 
>                                                 Masataka Ohta
> 
>

v2.23.0 | Report a Bug | By Email