Re: RRG thoughts (was [Bier] [pim] Q on the congestion awareness of routing protocols)
Toerless Eckert <tte@cs.fau.de> Sat, 17 December 2022 10:07 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 F3030C1516E7 for <routing-discussion@ietfa.amsl.com>; Sat, 17 Dec 2022 02:07:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.646
X-Spam-Level:
X-Spam-Status: No, score=-6.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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
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 mZgJmTsloYtf for <routing-discussion@ietfa.amsl.com>; Sat, 17 Dec 2022 02:07:02 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (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 1C932C14CF12 for <routing-discussion@ietf.org>; Sat, 17 Dec 2022 02:07:01 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id DC39E5484FC; Sat, 17 Dec 2022 11:06:54 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id C59434EC31D; Sat, 17 Dec 2022 11:06:54 +0100 (CET)
Date: Sat, 17 Dec 2022 11:06:54 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Joel Halpern <jmh@joelhalpern.com>
Cc: Dino Farinacci <farinacci@gmail.com>, routing-discussion@ietf.org, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
Subject: Re: RRG thoughts (was [Bier] [pim] Q on the congestion awareness of routing protocols)
Message-ID: <Y52Uvg5py0XWHDd5@faui48e.informatik.uni-erlangen.de>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <6299b96a-7f0f-2785-c945-80ca0d4404cc@joelhalpern.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/aUpV1nvbE7EtlSQgUOlknEF7CRE>
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, 17 Dec 2022 10:07:06 -0000
Joel: a) Purpose and opertions of IETF and IRTF are evolving both through new rules but also through new choices by leadership. I see this comparing some IRTH groups created recently vs. earlier. I see this in how we now have SIGs in OPS, i see this in AFAIK a growing set of groups having more interims or other in-between-full-IETF-meetings regular meetings since we have meetecho - just to name three examples. So i would appreciate if you could give concrete examples of what you think would be "not fitting" in your opinion. b) Some idea of how this could be structured: We use "routing-discussion" as the main communications forum. We designate some wiki page to capture proposed input (that has no other place in IETF, IRTF): drafts, presentations, external research papers/presentations. So the main work is to have folks who like chairs manage this. We designate a monthly slot 1..2 hours for the forum, but the slot is only active with a 2 week earlier invite when there is content (like a regular, but on-demand interrim). The content will consist of requested or invited talk/discussions (requested via mails/thread on routing-discussion). The main thing is to build the wiki up to be clear about procedures/goals: 1. It's free (just create free datatracker account if you do not have one). 2. Bring unfinished research / ideas to the forum, to present/get-feedback, can simply refer to your research paper (draft), no need for a draft submitted to IETF. 3. Meetings will have also open forum section so folks who can't even figure out 2. so far can ask questions. Of course, IETF note-well does apply (by mere use of standard IETF tools - list, meetecho or webex for the meetings (webex has live transcription, maybe also translation ? may make it a better tool than meetecho !). There needs to be promotion of this idea to research community of course. Not really difficult when one puts together flyers and hands them out to colleagues attending research conferences dabbling in routing. Its IMHO not really rocket science. And i don't claim above are the best ideas, but retainly better than business as usual. Its can also double as a kind of dispatch front-ending RTGWG . The main issue with RTGWG being that its a) more difficult to figure out how to get into free, b) more difficult to be productive if you attend remotely a primarily in-person event, c) some group of RTGWG participants does not like to see the WG spend so much time on non-WG work Cheers Toerless On Sat, Dec 10, 2022 at 01:28:38PM -1000, Joel Halpern wrote: > 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 -- --- tte@cs.fau.de
- Q on the congestion awareness of routing protocols Toerless Eckert
- Re: [pim] Q on the congestion awareness of routin… Greg Shepherd
- Re: Q on the congestion awareness of routing prot… Jon Crowcroft
- Re: Q on the congestion awareness of routing prot… Matt Mathis
- Re: [pim] Q on the congestion awareness of routin… Toerless Eckert
- Re: Q on the congestion awareness of routing prot… Toerless Eckert
- Re: Q on the congestion awareness of routing prot… Toerless Eckert
- Re: Q on the congestion awareness of routing prot… Masataka Ohta
- Re: Q on the congestion awareness of routing prot… Jon Crowcroft
- Re: Q on the congestion awareness of routing prot… Stewart Bryant
- Re: Q on the congestion awareness of routing prot… Jon Crowcroft
- Re: Q on the congestion awareness of routing prot… Masataka Ohta
- Re: Q on the congestion awareness of routing prot… Masataka Ohta
- Re: Q on the congestion awareness of routing prot… Jon Crowcroft
- Re: Q on the congestion awareness of routing prot… Bless, Roland (TM)
- Re: Q on the congestion awareness of routing prot… Carsten Bormann
- Re: Q on the congestion awareness of routing prot… Robert Raszuk
- Re: Q on the congestion awareness of routing prot… Curtis Villamizar
- Re: Q on the congestion awareness of routing prot… Masataka Ohta
- Re: Q on the congestion awareness of routing prot… Bless, Roland (TM)
- Re: [pim] Q on the congestion awareness of routin… Dino Farinacci
- Re: [pim] Q on the congestion awareness of routin… Dino Farinacci
- Re: Q on the congestion awareness of routing prot… Toerless Eckert
- Re: Q on the congestion awareness of routing prot… Matt Mathis
- RE: [Bier] [pim] Q on the congestion awareness of… Dirk Trossen
- Re: [pim] Q on the congestion awareness of routin… Jon Crowcroft
- Re: [pim] Q on the congestion awareness of routin… Masataka Ohta
- Re: [pim] Q on the congestion awareness of routin… Michael Welzl
- Re: [pim] Q on the congestion awareness of routin… Jonathan Morton
- Re: [Bier] [pim] Q on the congestion awareness of… Robert Raszuk
- OT and trimmed (was Re: Q on the congestion aware… Curtis Villamizar
- Re: [Bier] [pim] Q on the congestion awareness of… Luigi Iannone
- Re: [pim] Q on the congestion awareness of routin… Dino Farinacci
- Re: [pim] Q on the congestion awareness of routin… Masataka Ohta
- Re: [Bier] [pim] Q on the congestion awareness of… Masataka Ohta
- Re: [Bier] [pim] Q on the congestion awareness of… Robert Raszuk
- Re: [Bier] [pim] Q on the congestion awareness of… Masataka Ohta
- RRG thoughts (was [Bier] [pim] Q on the congestio… Toerless Eckert
- Re: Q on the congestion awareness of routing prot… Toerless Eckert
- Re: RRG thoughts (was [Bier] [pim] Q on the conge… Luigi Iannone
- Re: [pim] Q on the congestion awareness of routin… Toerless Eckert
- Re: RRG thoughts (was [Bier] [pim] Q on the conge… Joel Halpern
- Re: RRG thoughts (was [Bier] [pim] Q on the conge… Dino Farinacci
- Re: RRG thoughts (was [Bier] [pim] Q on the conge… Robert Raszuk
- Re: RRG thoughts (was [Bier] [pim] Q on the conge… Luigi Iannone
- Re: RRG thoughts (was [Bier] [pim] Q on the conge… Jon Crowcroft
- RE: RRG thoughts (was [Bier] [pim] Q on the conge… Adrian Farrel
- Re: RRG thoughts (was [Bier] [pim] Q on the conge… Abdussalam Baryun
- Re: RRG thoughts (was [Bier] [pim] Q on the conge… Toerless Eckert
- RE: [pim] Q on the congestion awareness of routin… Jeffrey (Zhaohui) Zhang
- Re: RRG thoughts (was [Bier] [pim] Q on the conge… Jeff Tantsura
- Re: RRG thoughts (was [Bier] [pim] Q on the conge… Robert Raszuk
- Re: [pim] Q on the congestion awareness of routin… Jonathan Morton
- Re: [pim] Q on the congestion awareness of routin… Jon Crowcroft
- Re: [pim] Q on the congestion awareness of routin… Michael Richardson
- Re: [pim] Q on the congestion awareness of routin… Jon Crowcroft
- Re: [pim] Q on the congestion awareness of routin… Adamson, Robert B CIV USN NRL (5592) Washington DC (USA)
- Re: [Bier] [pim] Q on the congestion awareness of… Toerless Eckert
- RE: [Bier] [pim] Q on the congestion awareness of… Jeffrey (Zhaohui) Zhang