Hi all, There were some discussions at RIPE91 about supporting the following draft. There is now a WG call to adopt the draft, so responses on the GROW mailing list to get the draft adopted would be greatly appreciated: https://mailarchive.ietf.org/arch/browse/grow/?q=draft-romijn-grow-rpsl-regi... For those that don't know the draft, it can be found on the IETF datatacker: https://datatracker.ietf.org/doc/draft-romijn-grow-rpsl-registry-scoped-memb... This draft addresses the ambiguity of references between sets in RPSL, where currently one set includes another by its RPSL primary key. As the same primary key may exist in multiple IRR registries, these references are ambiguous, while the referred objects sometimes have very different contents. The draft adds a new attribute where references to other sets must be scoped to a specific IRR registry. Specific resolving and validation rules ensure that we keep backwards compatibility with older RPSL objects, authoritative servers, and resolvers. At the same time, it provides benefits even with partial deployment With kind regards, James Bensley (he/him) [CompanySignature] Inter..link GmbH | Boxhagener Straße 80, 10245 Berlin, Germany | Managing Directors: Marc Korthaus, Theo Voss | Commercial Register: Amtsgericht Charlottenburg, HRB 138876 | VAT ID: DE281288887 | Email: hello@inter.link<mailto:hello@inter.link> | Web: inter.link<https://inter.link>