Hello, We would like to share our draft "Registry scoped members for RPSL set objects" with the working group: https://datatracker.ietf.org/doc/draft-romijn-grow-rpsl-registry-scoped-members/
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. There was some earlier discussion on the routing-wg list on this issue and how to resolve it, but it didn't lead to any practical solution. This new proposal 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. We welcome your feedback and discussion, though preferably on the GROW mailing list: https://mailarchive.ietf.org/arch/msg/grow/mdoTvD2vQBZqsDO0VRWRo-ADD3c/ Sasha ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/routing-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
