IETF Logo Mail Archive

Re: RRG thoughts (was [Bier] [pim] Q on the congestion awareness of routing protocols)

Dino Farinacci <farinacci@gmail.com> Sat, 10 December 2022 23:35 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66699C14F748 for <routing-discussion@ietfa.amsl.com>; Sat, 10 Dec 2022 15:35:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 dFUDwKr73eGm for <routing-discussion@ietfa.amsl.com>; Sat, 10 Dec 2022 15:35:50 -0800 (PST)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 1128EC14F743 for <routing-discussion@ietf.org>; Sat, 10 Dec 2022 15:35:50 -0800 (PST)
Received: by mail-pf1-x433.google.com with SMTP id d82so6164733pfd.11 for <routing-discussion@ietf.org>; Sat, 10 Dec 2022 15:35:50 -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=C6LmsZdekZxwZOh2cVeZ5mtUZosxBQuor40QzUuFud4=; b=D6igPjGGekzjxrmr9v7aF9+RmmtVpMcaT+/RwaNufYuH/m5e2ADJhykeg0vubyow7R 6qKfl0eE1IJlMwxzfrxOEeVXMN7LQ6aDdunnSp6AaAQ0pcoqElTtXpJRTkh7RNMFjIJT 1UK+cvKuX6btupMYBXSn/I1utxQKatWE4sbLPLnF2rZVPrUFd4W1cua2u/GMYkeilNCn SXc8/gZFWtrTm5Hf7d+Jl7uPozigAVZ8oRlpKdBJcAvgVvKKH5S5L1oP2wf9w+Bf8bja F0VzqN8n49O9eDENY2aFSyawfSsmZP42QbCdiy8vZRYHK7aS9pJI0kKoWrkB9uaNo4gk pFjA==
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=C6LmsZdekZxwZOh2cVeZ5mtUZosxBQuor40QzUuFud4=; b=d1QbYc+FLs7I3ziGE205S8EswymEqezo5JX01b1Zt7tPejI/ndzog7LyOliMowlDq+ gQQ+0GaDZajbDpkW0nwKMko3QK8gkuXR2TZNI0/ssKHu4Ug+fzLWCyXPdoIWL23UfxLN /LzHXr3zRGdoZWJzlDTqTVRHkjNXBRFUcLtXVQQHuzVHBGb941Xgk8DkCQ0IQAVUwPoI LmnalWiKX7p3qcNK3TzSn1YPME8gvyAzMGF8NDr+MlivuYrTesXxR6N/mCttfeNgRmtR STKlLmn889DSOmYJyJap47T5ERSzM5ZYpelMCXWY34ySAeNC45XeNh18ToEB8TnI0kPD sUyg==
X-Gm-Message-State: ANoB5pn07OV00WyajF2+lmEkMcyXi4IUnRlazdbTrp74+/D4AsXHVoeI KxGlfeGKaKtj0HSr7Lgc+DA=
X-Google-Smtp-Source: AA0mqf4yYrbRkFM/f0svwP3269xs+U4XwjURJi1bbGncY4g7FWtM1+blpcrNghHSW6fr1xvwevYZ3Q==
X-Received: by 2002:a05:6a00:213b:b0:576:f322:419f with SMTP id n27-20020a056a00213b00b00576f322419fmr11947991pfj.28.1670715349591; Sat, 10 Dec 2022 15:35:49 -0800 (PST)
Received: from smtpclient.apple ([2601:646:9600:d610:b5d3:d703:9589:ff3e]) by smtp.gmail.com with ESMTPSA id y13-20020aa79aed000000b00575c8242849sm3227676pfp.69.2022.12.10.15.35.48 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 10 Dec 2022 15:35:49 -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: RRG thoughts (was [Bier] [pim] Q on the congestion awareness of routing protocols)
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <6299b96a-7f0f-2785-c945-80ca0d4404cc@joelhalpern.com>
Date: Sat, 10 Dec 2022 15:35:46 -0800
Cc: Toerless Eckert <tte@cs.fau.de>, routing-discussion@ietf.org, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EFC4B5E0-90A8-4C71-959A-C25AD5989491@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> <2D989E7C-EBFB-42C4-9D55-F934A1437B19@gmail.com> <Y5M5PNT6PV/YsG/V@faui48e.informatik.uni-erlangen.de> <6299b96a-7f0f-2785-c945-80ca0d4404cc@joelhalpern.com>
To: Joel Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/W3sTUeRSIYbvHdIhbq0x6UoU1JQ>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area General Discussion list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Dec 2022 23:35:50 -0000

> The idea of a suitable forum for informal conversation between researchers, vendors, and operators, seems useful.  I do admit that I tend to be skeptical of regular meetings without agendas or clear purpose, as such things tend to devlove (in various different unpleasant ways.)  More importantly, this does not fit well with the purpose and operations of either the IETF or the IRTF.  So figuring out structure and rules (preferably somehow making everything discussed subject to IETF note well and similar policies) seems tricky.

Just have the meeting leader enforce a pre-approved agenda. And if the group votes for a long Q&A with a person at the mic no longer than 2 minutes, for example, it can work. Just needs to be enforced.

If you don't agree or violate what meeting leader enforces, you are asked to leave.

Dino

v2.23.0 | Report a Bug | By Email