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

Adrian Farrel <adrian@olddog.co.uk> Sun, 11 December 2022 18:07 UTC

Return-Path: <adrian@olddog.co.uk>
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 CC682C14CF0B for <routing-discussion@ietfa.amsl.com>; Sun, 11 Dec 2022 10:07:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.092
X-Spam-Level:
X-Spam-Status: No, score=-7.092 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_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 (2048-bit key) header.d=olddog.co.uk
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 sUwjf8rUUYIN for <routing-discussion@ietfa.amsl.com>; Sun, 11 Dec 2022 10:07:42 -0800 (PST)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BE67C14CF03 for <routing-discussion@ietf.org>; Sun, 11 Dec 2022 10:07:40 -0800 (PST)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta8.iomartmail.com (8.14.7/8.14.7) with ESMTP id 2BBI7YuF004939; Sun, 11 Dec 2022 18:07:34 GMT
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id CABBA46050; Sun, 11 Dec 2022 18:07:33 +0000 (GMT)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id BDA9F4604C; Sun, 11 Dec 2022 18:07:33 +0000 (GMT)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs2.iomartmail.com (Postfix) with ESMTPS; Sun, 11 Dec 2022 18:07:33 +0000 (GMT)
Received: from LAPTOPK7AS653V ([87.112.52.162]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.7/8.14.7) with ESMTP id 2BBI7Ucq011725 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 11 Dec 2022 18:07:32 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Luigi Iannone' <ggx@gigix.net>, 'Robert Raszuk' <robert@raszuk.net>
Cc: 'Jon Crowcroft' <Jon.Crowcroft@cl.cam.ac.uk>, 'Dino Farinacci' <farinacci@gmail.com>, routing-discussion@ietf.org
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> <CAOj+MMH524-GewjPbvHjUncqV1Q_VTEFf3SeSdaeeo-XGLUW9Q@mail.gmail.com> <117980CA-FA3E-414E-AC35-50E3752702F0@gigix.net>
In-Reply-To: <117980CA-FA3E-414E-AC35-50E3752702F0@gigix.net>
Subject: RE: RRG thoughts (was [Bier] [pim] Q on the congestion awareness of routing protocols)
Date: Sun, 11 Dec 2022 18:07:31 -0000
Organization: Old Dog Consulting
Message-ID: <049b01d90d8b$716b1a40$54414ec0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQFD4fO0UbWbhemGI0e04KcJ9Y08xQIq7InWAlI79ocBi8avygIUgYsQAqgUSmEBV6DJqAImfCXhAZpxtYmvFF2HsA==
X-Originating-IP: 87.112.52.162
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding; s= 20221128; bh=C9/YgrrKAIO8jX1F3RfrlU9QiL6JoUZfdQ2zYEeq7NA=; b=vTN eI7LEu6GosNRev5aDYpRIg4vLsqJ6n8O9T1S2HMeEs8Ncp3LTeh2xrevPp49YnRo 1NjwFP69glt4UcZQRxDmYMtSgeSe5AbBTV2p8LaH1dZV4/SpreLwb41YbcWMxPWg p234PVk/3bjmGQehkA1ScA316CHLeLzaADL9Gz08S2zPRyMJC4k+ue4miWxh7dPZ WoeyZ36R0kShRn7UDvagJJ0uY43ts/p0D/3EhP1DQODlPRZ/Z3RJpaZrmfdA33V/ oViTGYRbFsPpa5w/cP/Ne+5KBrKredoGicW4QH+F7yBREk+Gr3yf2ylzRKhLbymY NdVdRMOOWB1e6ulnTgg==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-27318.002
X-TM-AS-Result: No--19.190-10.0-31-10
X-imss-scan-details: No--19.190-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-27318.002
X-TMASE-Result: 10--19.190300-10.000000
X-TMASE-MatchedRID: Jm7Yxmmj9OnxIbpQ8BhdbIGD9MrmzQNzsBSA1tuZVSZ0Tsch72XSbFRG 1tpaU7lUmdGNf3KgVQk0jZmiiIwNTzaVcSw1Mqm236lQXQeyPFEiSMnphO25RbcIt210bWgISdp 3nQlC6CsKoiVTDA+B7BVXuF6cxvNl7jTtcyq422YpDEdiwJzEaUyQ5fRSh265tmNxkMfa5PQhgV U1JTxZmF5p3o7yf30gMG6PW0MNw7pyT9Lk7c70V/HkpkyUphL99mojSc/N3Qee9toQ6h6LE6jxn qHLJ3yJw7rSZQtYkH8Tj7WyCrz6xOmwi3JJ5cS1L7p//vLv4bPsOLuBdv6MMS196sn93sBvn9BE D1wLp16Ikv/RbiC5otez40ONsDlRl79sXVrKzZKOl15fZkS+ssqspZV+lCSLIiqlmO0FgHsziof F3qXu2qTvCVjHNK9X3A0Bu17t9z3xlOJuQNHlfQvBTB90+he+FJ7PgBJ+66lShO3/fRZx3IRMyN /ppM4nOyMuMTA7TZ6+gPhGSQqXaZcFdomgH0lngxsfzkNRlfIrN8z0HohG3voLR4+zsDTtAqYBE 3k9Mpw=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/nMUYE1AAtNND5IPGRmLeJ9dCoWQ>
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: Sun, 11 Dec 2022 18:07:47 -0000

I find myself in agreement with this thread.

A few of us (daniel King, Dirk Trossen, me) have been trying to run "side meetings" either at IETF meetings (virtual and physical) or as interims (virtual) to bring "interesting, routing-related research papers" to the IETF community. These meetings have been pretty well attended (although IETF-115 was a challenge for scheduling).

If I have it right, the Internet routes around problems. I think we can do that quite well by self-organising. 
- This mailing list is a good place for routing discussions (thanks to the ADs for making that clear).
- We can continue to bring routing research to the IETF community. Let's find recent papers and active research and bring the authors to IETF meetings or to interims to kick up some discussion.
- I know that the RTGWG chairs are happy to have occasional presentations in their working group, and even focussed interims if a topic is bubbling.
- The routing ADs seem to like the idea of including strategic and recognised papers in the Area meeting at IETF meetings.

I'd be happy to work with others (Luigi, Dirk, Dan, ...) to keep this seam of side meetings going.

Let's collect three or four proposals for presentations in Yokohama.

Best,
Adrian

-----Original Message-----
From: routing-discussion <routing-discussion-bounces@ietf.org> On Behalf Of Luigi Iannone
Sent: 11 December 2022 13:10
To: Robert Raszuk <robert@raszuk.net>
Cc: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>; Dino Farinacci <farinacci@gmail.com>; routing-discussion@ietf.org
Subject: Re: RRG thoughts (was [Bier] [pim] Q on the congestion awareness of routing protocols)

Hi,

> On 11 Dec 2022, at 00:56, Robert Raszuk <robert@raszuk.net> wrote:
> 
> Joel at all,
> 
> > The idea of a suitable forum for informal conversation between
> > researchers, vendors, and operators, seems useful.
> 
> The crux of the matter is that researchers stay around SIGCOMM, vendors stick to IETF to push RFCs and real operators prefer to go to local NOGs or Apricot/RIPE/NANOG or IXP centric meetings. Then we have a zoo of those "OPEN" everything venues. 

Indeed, the crucial part is the role of the “leaders”, let’s say 2 or 3 chairs (to use IETF terminology) that spend time looking around and trying to bring together these different communities on topics that span among all of them. Building an agenda, but also gathering the topics of interest.

Another point that I made in the draft I have mentioned is about increasing ties with academics from the different venues.
IETF 115 was in London, Jon Crowcroft showed up to the side meeting, which was good.
IETF 116 is in Japan, there are a few researcher there that is worth inviting.
And so on and so forth for the different places where the IETF  will be held.
Even in returning places would be nice to have updates “what did happen to that nice idea you presented last time…”

There is potential for a lot of things….  

I do believe this is possible and would love to have help to making this happen.

Ciao

L.



> 
> As an industry we have an issue - we no longer communicate on the tech level unless you have folks attending and participating in all of the above. And I am not guessing here ... I am (trying) to be part of all of the above. It is no longer how IETF started in the early days. 
> 
> Just take a look at SCION enthusiasts. Observe their struggle to educate/sell the idea. I am not yet convinced that what they cooked is solid, but the effort they are taking gives you a good view on the present situation. 
> 
> Cheers,
> R.
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www.ietf.org/mailman/listinfo/routing-discussion