Re: [pim] Q on the congestion awareness of routing protocols

Toerless Eckert <tte@cs.fau.de> Fri, 09 December 2022 13:46 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 587A5C14CE28; Fri, 9 Dec 2022 05:46:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.649
X-Spam-Level:
X-Spam-Status: No, score=-6.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 WGsCNVH2v0M7; Fri, 9 Dec 2022 05:46:56 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDF5AC14F737; Fri, 9 Dec 2022 05:46:49 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 048BD5486EE; Fri, 9 Dec 2022 14:46:46 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id EAB1E4EC260; Fri, 9 Dec 2022 14:46:45 +0100 (CET)
Date: Fri, 09 Dec 2022 14:46:45 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
Cc: Dino Farinacci <farinacci@gmail.com>, Stewart Bryant <stewart.bryant@gmail.com>, Matt Mathis <mattmathis=40google.com@dmarc.ietf.org>, BIER WG <bier@ietf.org>, tsv-area@ietf.org, pim <pim@ietf.org>, routing-discussion@ietf.org
Subject: Re: [pim] Q on the congestion awareness of routing protocols
Message-ID: <Y5M8RSjDuTLqJ/+v@faui48e.informatik.uni-erlangen.de>
References: <CAH56bmBnqi4peTWUXOVy0KRRXRc1L7TP+atFfVF6qb_OKBMBwg@mail.gmail.com> <C303F9BF-F96A-4710-A4B5-4228807C07F7@gmail.com> <52907137-CA5A-4042-AB2C-23FD9B032210@gmail.com> <E1p2SAw-006HQa-3s@mta0.cl.cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E1p2SAw-006HQa-3s@mta0.cl.cam.ac.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/WueSa-0A05rWRsbpPGIypfDy9BE>
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: Fri, 09 Dec 2022 13:46:57 -0000

On Tue, Dec 06, 2022 at 07:15:31AM +0000, Jon Crowcroft wrote:
> path exploration? but consider the shadow pricing...
> 
> the tradeoff between convergence rate and congestion control seems to
> be something that ought to be put on a more systematic grounding

You folks are all thinking way beyond the point i was making and looking for support:

In PIM, we have potentially gigantic burst of datagrams without any
specification of pacing sent to routers across a network core (with easily
likelyhood of path congestion). Such a totally non-congestion aware sending
of protocol packets should not be permitted anymore for new RFC IMHO
and i am just baffled how this is permitted anymore by the IETF. Where
is adult supervision by TSV when we need it ;-)

Yes, the incast issue is an interesting aspect, but i have not seen good
simulations whether / to-what-extend it would happen in the PIM/BGP cases,
but i would bet any sum, that a TCP solution, as bad as it may be will
outperform the no-congestion-control periodic burst solution of (datagram) PIM.

Cheers
    Toerless