IETF Logo Mail Archive

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

Dino Farinacci <farinacci@gmail.com> Mon, 05 December 2022 20:36 UTC

Return-Path: <farinacci@gmail.com>
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 35EC9C1522AE; Mon, 5 Dec 2022 12:36:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.com
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 8gG_WKp90ik8; Mon, 5 Dec 2022 12:36:27 -0800 (PST)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 5A877C14F743; Mon, 5 Dec 2022 12:36:27 -0800 (PST)
Received: by mail-pl1-x62a.google.com with SMTP id w23so11921138ply.12; Mon, 05 Dec 2022 12:36:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=iByEQCb90sf4f9Wm0hEe0dBO+jhFTwhXo6Xd7PGjDCM=; b=eIcCDnG5+cxRlLS6yIifO1HKk5P8/QHS223LQ+aXSPpRT6Q+2KkldplvhlsLAn1F7o cpZ9wNhPNWUmsQYClTNZgJiZL5VKvnASH9smzJTdwSlnjFE+ERJZ8eMSiUNZM3XtmDdK p6gepi1Ut6Ny6h12YhXOPGkiCzNxx2F0+BB9VKacwa0ptg8Jx8gd4tJBKSR5WTuisLEj 5WbsWJgkakSdHqLs4ZrofxXpxj9Z+zR/57Q2/ohieiq2rZ/N2GohyvEhBHUJPIxkRb/w rKDdbbnSQNTf4ueKkcfDmvE3EFXXsNsbPjUS2EGUwnuzsMk9hRamA8pS4BXdYPjgbQn3 1Bsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=iByEQCb90sf4f9Wm0hEe0dBO+jhFTwhXo6Xd7PGjDCM=; b=Z/J89VuGff4zBw1DCE5JKYwy756/hbGKMff4/HiJjVHNVngQg/SbsuH7OpH9ufssj8 bVXezg0h8QKYvdRT1oy03I0bX/T1h+IyNFMwou1/GyazLWfeIwNi3l593YJAGy7Ahl0f GAzBf5xDroCT3R42xQagcOUKENtMYBuzeRMZZmgmF1vY1w3uOY5VyJaX9IzTAV5WtW8d KubVqXeT+wHirv3PvIVrdQPffqkXZk7BlHrT8Q7yNZAFYZcCBJXuMP7oLmXyFdC68y7H K5VilCx0B8S0rok/LL4SVYA9tS20tovRsyMdNl7AOjE5nLLwAVythINMdeDnbBFEDXjX oCWg==
X-Gm-Message-State: ANoB5pmnB316tHUnQpNOnidXeBvoGW8ijWK1Hmbgk3TBzdoemZt2lyUF 4ChhZVGP9pAwkOZyRJaioZI=
X-Google-Smtp-Source: AA0mqf40Eal+J2SU5JA+VJJEcUJvrK7gwbfxMpGftmj2gpwZjR/7RrHURv9PxMrjonPUjqniAGr0CQ==
X-Received: by 2002:a17:90a:5991:b0:218:47f1:b47b with SMTP id l17-20020a17090a599100b0021847f1b47bmr89935975pji.201.1670272586732; Mon, 05 Dec 2022 12:36:26 -0800 (PST)
Received: from smtpclient.apple ([2601:642:4c01:2539:b469:c932:4569:6bec]) by smtp.gmail.com with ESMTPSA id u207-20020a6279d8000000b00575da69a16asm10668197pfc.179.2022.12.05.12.36.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Dec 2022 12:36:26 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Subject: Re: [pim] Q on the congestion awareness of routing protocols
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <C303F9BF-F96A-4710-A4B5-4228807C07F7@gmail.com>
Date: Mon, 05 Dec 2022 12:36:25 -0800
Cc: Matt Mathis <mattmathis=40google.com@dmarc.ietf.org>, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>, BIER WG <bier@ietf.org>, tsv-area@ietf.org, pim <pim@ietf.org>, routing-discussion@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <52907137-CA5A-4042-AB2C-23FD9B032210@gmail.com>
References: <CAH56bmBnqi4peTWUXOVy0KRRXRc1L7TP+atFfVF6qb_OKBMBwg@mail.gmail.com> <C303F9BF-F96A-4710-A4B5-4228807C07F7@gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/WMfjaRKvy2E-bgVnTYJ4Cudc3mM>
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: Mon, 05 Dec 2022 20:36:31 -0000

> One thought is that we set up a shadow RRG operating independently of the IETF meeting but meeting concurrently and at the same location. This is what BoFs used to be before the IETF apparatus got hold of them and formalised them. We can still use the draft infrastructure. If we cannot have a IETF list, there is groups.io or similar. All a bit like Internet Routing where we route around damage to the infrastructure.

I'd be all for this idea.

Dino

v2.23.0 | Report a Bug | By Email