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

Jeff Tantsura <jefftant.ietf@gmail.com> Sat, 17 December 2022 22:40 UTC

Return-Path: <jefftant.ietf@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 5D93DC14F73D for <routing-discussion@ietfa.amsl.com>; Sat, 17 Dec 2022 14:40:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, MIME_QP_LONG_LINE=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_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=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 NiyWVEt-Aug5 for <routing-discussion@ietfa.amsl.com>; Sat, 17 Dec 2022 14:40:28 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 96EF8C14F737 for <routing-discussion@ietf.org>; Sat, 17 Dec 2022 14:40:28 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id 3-20020a17090a098300b00219041dcbe9so5669505pjo.3 for <routing-discussion@ietf.org>; Sat, 17 Dec 2022 14:40:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:date:cc:in-reply-to:from:subject :mime-version:content-transfer-encoding:from:to:cc:subject:date :message-id:reply-to; bh=0gxMnceL4vnta7qmPRZ0XYdaW35wxzwiBCI76QmjPS4=; b=nmrmlKNsMceeahaksoHdIHZXCECT3TN9IwTMmHY1rIqhz/H6A6Xz9UYk4ULWN61wxP KqnTNmwSy1Gunkcaj2KiAcA4a9/lWJzG/PTOhaUUUVRH8SD7MADc2RVaNKDMyEZNGsxK IJEydGERN68RCBYO3zblQWKYq0ib6K8luz4zfyZ0Q7V/SzTv8S9atb2D+b8gFswk4W6J /a2hlzffoBdSPhtuif8QcFoF9z7qgKwDGR8ogJQjM2FqgP3LYX3jUY0m1CTWG3rBE3/+ 1D6zXETxEVc3Q0pUzYrTx0J2Rp0DmgmA77uV89bgyxkWmzmxU6o5AqYJqraB9M90FHgE 7FJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:date:cc:in-reply-to:from:subject :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=0gxMnceL4vnta7qmPRZ0XYdaW35wxzwiBCI76QmjPS4=; b=T7me4R1Xiv7b9YJThHHyl0idxh629t9/7Nzc/FcGjAGZw22v9eJVK9/ZpgmIb/8yvC JQ4ToJklGgFXYhZ48MWY/P3i+DZlDw+D6b/J7LxxXo6OdDyP+etkSs4j2shEwQme7z07 vZ3Wdb0SeFQ82lJSuX2ztHYXv8CezMWbjWERECpkIU8fcYEoq1LjzahJEjz5pLXMd7iD jSMSN45++Hh5O1d28HrFtbIp2mbU1fBh4aa9SqEEM8PFU+1Cm/s6tOO5LWMU2KX2owz1 p3qr8zpXmm3cvVK9oNCrlvGjVukhcs7dCczetq/6F6SKYjjDMppR55llpedpXZHt0YmD wWTA==
X-Gm-Message-State: ANoB5pm4BV7yfcm7TTg5tTrrJkXCgIaOclvTCV+n5XK1THRsBT5FoOzI M1N2gEGrFWsIGWMvCeO/1oZB3mPNE5s=
X-Google-Smtp-Source: AA0mqf59W5IxvrtrEpX6P1ndj6gZiQD/fE4BdYARrf08rEsJFXp862S83G/WjgIKN8D4l83Hc5zwPg==
X-Received: by 2002:a05:6a21:9989:b0:9d:efbe:e608 with SMTP id ve9-20020a056a21998900b0009defbee608mr52280819pzb.36.1671316827432; Sat, 17 Dec 2022 14:40:27 -0800 (PST)
Received: from smtpclient.apple ([2600:6c4e:2200:1fac:143d:ab8:3754:cc14]) by smtp.gmail.com with ESMTPSA id f12-20020aa7968c000000b0057726bd7335sm3621721pfk.121.2022.12.17.14.40.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 17 Dec 2022 14:40:26 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: RRG thoughts (was [Bier] [pim] Q on the congestion awareness of routing protocols)
From: Jeff Tantsura <jefftant.ietf@gmail.com>
In-Reply-To: <049b01d90d8b$716b1a40$54414ec0$@olddog.co.uk>
Cc: Luigi Iannone <ggx@gigix.net>, Robert Raszuk <robert@raszuk.net>, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>, Dino Farinacci <farinacci@gmail.com>, routing-discussion@ietf.org
Date: Sat, 17 Dec 2022 14:40:15 -0800
Message-Id: <365918FC-2AF7-4D8F-9294-21FFE453A5E3@gmail.com>
References: <049b01d90d8b$716b1a40$54414ec0$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: iPhone Mail (20C65)
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/G8SkrgqKELzeUE3PQoUpJzovcac>
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 22:40:30 -0000

Speaking as RTGWG chair - we are to continue bringing up “interesting/routing relevant” topics to wg meetings. We would also be happy to have a more structured (through interims/IETF meetings) dedicated time to report/discuss top ideas that came up from the yet to be established RRG/SiG/any other form. 
——————————-
BGP/TCP part

BGP with Add-Path  ALL used indiscriminately in large networks is indeed a nightmare (I have observed BGP RIBs of 60M routes), you can do the math. While with some creativity, can be reduced (e.g policy based Add-Path with BW aware advertising), deployment of such technologies and relevant tooling is anything but trivial.

Cheers,
Jeff

> On Dec 11, 2022, at 10:08, Adrian Farrel <adrian@olddog.co.uk> wrote:
> 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
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion