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

Joel Halpern <jmh@joelhalpern.com> Sat, 10 December 2022 23:28 UTC

Return-Path: <jmh@joelhalpern.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 A5824C14F748 for <routing-discussion@ietfa.amsl.com>; Sat, 10 Dec 2022 15:28:46 -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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 (1024-bit key) header.d=joelhalpern.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 CQdvI1JKLxUp for <routing-discussion@ietfa.amsl.com>; Sat, 10 Dec 2022 15:28:43 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 0EBEAC14F743 for <routing-discussion@ietf.org>; Sat, 10 Dec 2022 15:28:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4NV3x66RRZz1pZsF; Sat, 10 Dec 2022 15:28:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1670714922; bh=mLKKhTUjGnBrhPu8iBYWGvEOiIIyrogBQ49VZzo0K1s=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=CZWHCNBqI+tgbnuo9/7OpF+n44C73okSg/DuzkctL1L5hkteBT0xshPfJoHjLh+0U 4J4lrhy+Vgv4OJciKCXLTvvIFRwDfJY1SCj7roTdtY1S2vVfRxUPj/kYW14fUkHUvx NFHBNZfuvGKivyipR1WA7DkygN/+gcrQLNYdfyQk=
X-Quarantine-ID: <Vs0HwqeK9TFn>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.21.74] (unknown [50.233.136.230]) (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 mailb2.tigertech.net (Postfix) with ESMTPSA id 4NV3x55gR4z1pNGb; Sat, 10 Dec 2022 15:28:40 -0800 (PST)
Message-ID: <6299b96a-7f0f-2785-c945-80ca0d4404cc@joelhalpern.com>
Date: Sat, 10 Dec 2022 13:28:38 -1000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1
Subject: Re: RRG thoughts (was [Bier] [pim] Q on the congestion awareness of routing protocols)
Content-Language: en-US
To: Toerless Eckert <tte@cs.fau.de>, Dino Farinacci <farinacci@gmail.com>
Cc: routing-discussion@ietf.org, Jon Crowcroft <Jon.Crowcroft@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> <2D989E7C-EBFB-42C4-9D55-F934A1437B19@gmail.com> <Y5M5PNT6PV/YsG/V@faui48e.informatik.uni-erlangen.de>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <Y5M5PNT6PV/YsG/V@faui48e.informatik.uni-erlangen.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/fBUzC1DypmcYOiiCJUkevC4LAAM>
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:28:46 -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.

Yours,

Joel

On 12/9/2022 3:33 AM, Toerless Eckert wrote:
> On Tue, Dec 06, 2022 at 12:54:57PM -0800, Dino Farinacci wrote:
>>> path exploration? but consider the shadow pricing...
>> Just something semi-formal where we can meet regularly. But first, please lets articuulate the problem very clearly. And bring operators in so they can confirm the problem that researchers are stating are real problems that need solving.
> I actually would love to just have a standing forum to better bring routing researchers
> together with industrial routing experts. Aka: not focussed on a specific issue
> (as Tony's past RRG instance). E.g.: where researcher can ask questions to the experts, or propose
> research and ask if/how this is useful to the industry, and where industry folks can
> ask for researchers to look into specific issues (i think there are for example a lot of
> simulations to investigate behaviors that we'd like to have from the undustry).
>
> Not sure if "Research Group" is the right name for this. I think it would be a lot
> closer to the SIG concept (https://wiki.ietf.org/en/group/iesg/specialinterestgroups),
> except that that concept was built and specified around interaction between IETF
> and operational considerations of a specific community. Not on bringing more researchers
> back to the IETF.
>
> We do have a subset of what i think such an RRG would do in rtgwg - researchers bring ideas -
> and then they most often figure out that they can only proceed when they throw themselves
> fully into the RFC process (which most of them cannot/wantnot do). And from what i
> understand even this is not always welcome by rtgwg, because it does take a significant
> amount of time that folks feel should better be spent on actual WG deliverables.
>
> Of course, i am mostly interested in the ietf->research direction, e.g.: where the IETF
> community can better raise the questions of interest to be researched because the way i
> see it, there is no forum whatsover for this part.
>
> Cheers
>     Toerless
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion