IETF Logo Mail Archive

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

Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk> Sun, 18 December 2022 09:03 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 84255C14CEE1; Sun, 18 Dec 2022 01:03:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 1yN49zDBD1eI; Sun, 18 Dec 2022 01:03:51 -0800 (PST)
Received: from mta2.cl.cam.ac.uk (mta2.cl.cam.ac.uk [IPv6:2a05:b400:110::25:2]) (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 E5398C14F722; Sun, 18 Dec 2022 01:03:50 -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-Transfer-Encoding: Content-ID:Content-Type:MIME-Version:References:In-reply-to:Subject:cc:To: From:Sender:Reply-To: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=evpR9bEk2jDVmLQguXHjghmsdZhNCbbE8PTXsuN5yFY=; t=1671354230; x=1672218230; b=m3K/z6ZMCsefOZbfgUSML/MrIxCEkMSCAZKbMeGx6IEaSTVDAbnU0Z09qJVgpexMMbMN6AwyPl ql5wbp1mPD7uIJxLK5O1RlgCS4Pn756ryTwr9o/Ok08dBsRBdnQKqDIpAp2ro8rtgZVquayeq4N3Z 8TpN1+dK388omqvEk/h/FOGHjvQzZgq6suJiCx3Hcbx6M+sKoPuNY0Oz2hNCIjv0GptLh/GMqlwGU KICOb6jQwWnWkuLJBqry77NOpswMZ7gtBTnYampsE8d2tgkHEFr0F1EZGQCc/7ufH8qLT0jnUgreS nbJgbnsXNleaQPmpV7dUOp24CNNnaPim1ZS4Q==;
Received: from ely.cl.cam.ac.uk ([2001:630:212:238:8cfa:7eff:feb6:efd7]) (dnseec=no) by mta2.cl.cam.ac.uk:587 [2a05:b400:110::25:2] with esmtp (Exim 4.93) id 1p6paD-0058T3-O6 (envelope-from <Jon.Crowcroft@cl.cam.ac.uk>); Sun, 18 Dec 2022 09:03:45 +0000
From: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
To: Jonathan Morton <chromatix99@gmail.com>
cc: "Jeffrey (Zhaohui) Zhang" <zzhang=40juniper.net@dmarc.ietf.org>, BIER WG <bier@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>, Matt Mathis <mattmathis=40google.com@dmarc.ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>, pim <pim@ietf.org>
Subject: Re: [pim] Q on the congestion awareness of routing protocols
In-reply-to: <607179AB-1603-4D8A-84FF-D379E1C57AB4@gmail.com>
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> <Y5M8RSjDuTLqJ/+v@faui48e.informatik.uni-erlangen.de> <BL0PR05MB56529DBC5D9299428B0D2A84D4E79@BL0PR05MB5652.namprd05.prod.outlook.com> <607179AB-1603-4D8A-84FF-D379E1C57AB4@gmail.com>
Comments: In-reply-to Jonathan Morton <chromatix99@gmail.com> message dated "Sun, 18 Dec 2022 09:11:50 +0200."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <695648.1671354225.1@ely.cl.cam.ac.uk>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 18 Dec 2022 09:03:45 +0000
Message-Id: <E1p6paD-0058T3-O6@mta2.cl.cam.ac.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/O7Od3H6-lUgiIqI4jiztSRnKj8I>
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: Sun, 18 Dec 2022 09:03:55 -0000

Yes, additionsally, though, we can learn lessons from 
data centers where there is a whole body ofwork on dealing with
many-to-many (e.g. apps using map/reduce platforms and similar) 
that cause congestion in  ways that might often be analgous to control
plane traffic between routers of many kinds - this work post dates 
most the TFRC work (though usually is baselined on that for the
pairwise case) - way back when saly & van wrote this from the routing
perspective:
https://www.icir.org/floyd/papers/sync_94.pdf

a few years back we did this
https://www.usenix.org/system/files/conference/nsdi15/nsdi15-paper-grosvenor_update.pdf
which is from the data center, swtch queueu perspective
(so about 75% non relevant) but table 2 on page 13 might 
give some ideas...

cheers
jon
p.s. some people might like that you can click on the graphs in our
paper and you get to go to the link for pages that hold code and data


> > On 17 Dec, 2022, at 4:32 pm, Jeffrey (Zhaohui) Zhang 
> <zzhang=40juniper.net@dmarc.ietf.org> wrote:
> >
> > - There are situations where a non-TCP based solution is needed even 
> when a parallel TCP-based option is also present, so we can not simply 
> disallow the former. We can discuss examples separately (one example is 
> actually PIM as BIER overlay vs mLDP/BGP as BIER overlay).
> 
> There are also congestion control algorithms that don't rely on an 
> underlying TCP session, such as TFRC (TCP Friendly Rate Control).  
> Possibly these could be applied to existing protocols.
> 
>  - Jonathan Morton
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion
>

v2.23.0 | Report a Bug | By Email