IETF Logo Mail Archive

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

Michael Richardson <mcr@sandelman.ca> Sun, 18 December 2022 21:22 UTC

Return-Path: <mcr@sandelman.ca>
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 444E8C14F692; Sun, 18 Dec 2022 13:22:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 KS6Lnq6gLiU1; Sun, 18 Dec 2022 13:22:36 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B4C2C14CE34; Sun, 18 Dec 2022 13:22:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id F2C4D38993; Sun, 18 Dec 2022 16:49:47 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xf2XG-uC8X2n; Sun, 18 Dec 2022 16:49:43 -0500 (EST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id D8D5B38991; Sun, 18 Dec 2022 16:49:43 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1671400183; bh=CbgQZejEi1/7ar339zypIzJaRNiZXmAOp0yqq1/i2Vw=; h=From:To:Subject:In-Reply-To:References:Date:From; b=bau7nhBMYcFLPVrOn2xxo0TWLaRzqgShKMK7pNztYGV/cq4syLe4ezxRRz1X4AxTg kF/5bdmpdHRXpOQl0EFfP2fWsGuRzc8EI8Exg2hcx8pytVw8F+OmxGiRBGZnpkvep9 HINVHLhkV3dMl+FAwQKbARKTOC3V89b7o0YbgHvfhkIOLuHDnQ/d12r7fMSq9xQLCL /IzBpgAlluFfk81/5HvVv3Yq/B2km3wuwDu4h57K54io0HXXExrQy811SuYEYvqdZu aBNFIliou09VIMJ/2J8FXLBgXm+Nnto7J8d2CBObmfPEglELF3oSPQAXwnH1ajgVjg FXQCq1mANtHXQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7FE591D5; Sun, 18 Dec 2022 16:22:29 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>, 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>, pim <pim@ietf.org>
Subject: Re: [pim] Q on the congestion awareness of routing protocols
In-Reply-To: <E1p6paD-0058T3-O6@mta2.cl.cam.ac.uk>
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> <E1p6paD-0058T3-O6@mta2.cl.cam.ac.uk>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sun, 18 Dec 2022 16:22:29 -0500
Message-ID: <9119.1671398549@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/tkGqTxMp6bsKzU2lHw6BaatByso>
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 21:22:40 -0000

Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk> wrote:
    > 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

for instance, I think, this recent talk:
https://netdevconf.info/0x16/session.html?keynote-ousterhout
(I haven't watched it, and I couldn't be at netdev this time)

I think that netdevconf is a good example of connecting IETF/academia and the
R-parts of BigTech.

Also there is:
     Semantic Address Routing and Hardware - SARAH
     SARAH@jiscmail.ac.uk

v2.23.0 | Report a Bug | By Email