[GROW] Re: draft-bensley-rpsl-exclude-members

James Bensley <lists+ietfgrow@bensley.me> Thu, 23 April 2026 14:45 UTC

Return-Path: <lists+ietfgrow@bensley.me>
X-Original-To: grow@mail2.ietf.org
Delivered-To: grow@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B17B0E1BF55F for <grow@mail2.ietf.org>; Thu, 23 Apr 2026 07:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776955543; bh=fhsghD1AUvXFG100iddSS5Xf9ykLev4YpWVYsnG/xtg=; h=Date:To:From:Subject:In-Reply-To:References; b=g+u0CZ3TXjI0VEf9y3+VlCQYLiAh9FfSmMmPDI7LY5c+BPCf2iTBNnkhm1PqKLFMT VdSpRKi+CRCibuAK5sItpxmwCNoiEGEvKLYG9nhpuWcHK/IlJrcgkPkNj4fu6UcTtQ StgaM1D6uQR6SMiYG13QKVgnaikRipS1tttLnZbw=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 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_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=bensley.me
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hlbHrs2S1Rrx for <grow@mail2.ietf.org>; Thu, 23 Apr 2026 07:45:40 -0700 (PDT)
Received: from mail-106117.protonmail.ch (mail-106117.protonmail.ch [79.135.106.117]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A6D8CE1BF169 for <grow@ietf.org>; Thu, 23 Apr 2026 07:43:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bensley.me; s=protonmail; t=1776955378; x=1777214578; bh=fhsghD1AUvXFG100iddSS5Xf9ykLev4YpWVYsnG/xtg=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=DLb9KmGfFsdtrsUaezh18lRuGIh8IvC25JYhTGMJAO1kMMTRaJX5lk5IaeJWMwz7B eiTqWqtjWfDOA/zG6XUprJ2PsxcC0f+RMQRTdD/GQExpUC1BsuHGEKVa7wB7GsLd37 yYDhjP1zIlVLyiZ1tEEqi4HeKHZnOTunolajhFnQU3QduUf2BqzX/ATkFChGjRpFm/ ofmDgXufyop0chZujD7hl3n42aBl6Ip7+6d2/elBKYuUDZ+q27rq6p18/1lXhLlbrR kkU5jvm24bVjH9nuzfxq7XPGmmKF27pPdJXS4IIWmBK4SDR1IANcIo5BjTIX3UdaPS f3UUmKhYSdiZQ==
Date: Thu, 23 Apr 2026 14:42:54 +0000
To: "grow@ietf.org" <grow@ietf.org>, Nick Hilliard <nick@foobar.org>
From: James Bensley <lists+ietfgrow@bensley.me>
Message-ID: <JPo6t8DOknmgJNZW2Z5xiXUsyjVL_BVdh-gw3jjeGyfEVumiglSL_9gVjqC344C4ZtFkl3iMzjQdEOCfPjTXyb76k50CBGhOZReDjs5IjxQ=@bensley.me>
In-Reply-To: <c86fdd2a-5ed2-ac34-c0e4-1a387003183f@foobar.org>
References: <Djrh257skbQQwLkpqteXHN0KWxEbdERnSBG8KW7YQeZVj2pNpx0gqG-r-OWKN2p1XAOhcanY3jF7Amu-mKJSFT_MCZEMtiTsaMFpaELlGGM=@bensley.me> <c86fdd2a-5ed2-ac34-c0e4-1a387003183f@foobar.org>
Feedback-ID: 49756985:user:proton
X-Pm-Message-ID: 4d88c6964c0332b471faf22f13fd1fd0518d7d3e
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="------252beb03ad11d7bd8c48254ded1bbf9303fb9fc7b54aeb139f6b9f445a76065d"; charset="utf-8"
Message-ID-Hash: C3SJ6SAJQ3MKRVWMWZCHWANDTRUFMS7A
X-Message-ID-Hash: C3SJ6SAJQ3MKRVWMWZCHWANDTRUFMS7A
X-MailFrom: lists+ietfgrow@bensley.me
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-grow.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [GROW] Re: draft-bensley-rpsl-exclude-members
List-Id: Grow Working Group Mailing List <grow.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/c8W5O4t5t_8SZCtjGSVm5W5qPGs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Owner: <mailto:grow-owner@ietf.org>
List-Post: <mailto:grow@ietf.org>
List-Subscribe: <mailto:grow-join@ietf.org>
List-Unsubscribe: <mailto:grow-leave@ietf.org>

Hi Nick,

Thanks for providing some feedback.

On Thursday, April 16th, 2026 at 15:57, Nick Hilliard <nick@foobar.org> wrote:

> So, yes. RPSL did try the set theory thing and in theory this idea could be workable, maybe.
> 

> Flicking back through rfc2622, I'm reminded of the horrors of mbrs-by-ref. I know it's inexcusably poor taste, but I can't help wondering whether you should also include a excl-mbrs-by-ref? Probably better to leave this for an April 1 RFC.

I have a split opinion on this - it seems like a valid request to me, but few initial thoughts are:

1. I can use the proposed exclude members field to exclude anything, included sets included by mbrs-by-ref (although not as efficiently, I would have to specify each RPLS key to excluded, so it would just be an efficiency gain to excl-mbrs-by-ref, but that leads me to 2...)

2. Some sort of excl-mbrs-by-ref might exclude too much, I only want to exclude some stuff covered by the maintainer so I'll still need to fall back to the proposed exclude members field to do a partial exclude?

3. My understanding is that mbrs-by-ref isn't used that much, so is this worth it?

This is off the top of my head and not thought through in depth. I can try and pull up some numbers on mbrs-by-ref usage if you think it worthwhile?

> Firstly, any output is going to be acutely dependent on how draft-romijn-grow-rpsl-registry-scoped-members operates. I haven't got to that yet in my ietf draft consumption backlog, but my first thoughts would be that the source:: scope would need to be applied aggressively to child objects (maybe it is already).

Due to being a co-author of draft-romijn-grow-rpsl-registry-scoped-members, that is fully catered for in this document.

> There's plenty of scope for exclusion to create operational problems. E.g. what happens when you have different sets which reference each other and then one of them is configured to include the other as an exclusion? There's no shortage of foot-guns here.

I have tried to think about this; I couldn't come up with a foot gun scenario, and I had already thought through stuff like order-of-operations type stuff that might arise. See section "3.3. Cumulative Excludes", if I've missed some scenario which leads to a new foot gun I haven't foreseen, please let me know, I obviously want to avoid that.

> A complete set theory implementation would ideally include operators for union, intersection, complement and all that. You can synthesize it kinda with a simple exclusion mechanism, but I wonder about data consistency and general flexibility.
> 

> There are two main problems with RPSL. One is grammar flexibility, of which there is very little, which is why any extension needs a new key mechanism defined. The second is that it inherently requires symbolic expressions, which increases the complexity of the parser.
> 

> So, if I were approaching this - which I'm not - I'd might be tempted to look at this from the point of view of pure set theory and design a key which allowed complex set manipulation grammar. I.e. create a full mechanism for symbolic manipulation of as-sets. Any existing code implementation already needs to deal with a good deal of symbolic manipulation, so this may not be as problematic as it seems at the outset.

I'm split on this, like the earlier point - I see it as a valid point, but like the earlier point, it's not clear to me how worthwhile this would be. I think most people are only interested in including everything in set X, and for some of us, to then exclude a few bits (hence the document). I'm not aware of people with more syntactically advanced use cases (I'm happy to be corrected here).

> I'd also ditch extending route-set objects - no-one uses them really. Also draft-romijn-grow-rpsl-registry-scoped-members does not apply to route-sets, so you'd have a lot of work to do if you wanted to make this work properly.

Happy to :D My opinion was that route sets are basically dead, but I felt that if I left them out, the first feedback I'd get is from the one network still using them "WHY U NO ROUTE SETS!!!".

With kind regards,
James.