Hello, We would like 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. 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. We welcome your feedback and discussion. Sasha and James > On 21 Feb 2025, at 12:20, internet-dra...@ietf.org wrote: > > A new version of Internet-Draft > draft-romijn-grow-rpsl-registry-scoped-members-01.txt has been successfully > submitted by Sasha Romijn and posted to the > IETF repository. > > Name: draft-romijn-grow-rpsl-registry-scoped-members > Revision: 01 > Title: Registry scoped members for RPSL set objects > Date: 2025-02-21 > Group: Individual Submission > Pages: 10 > URL: > https://www.ietf.org/archive/id/draft-romijn-grow-rpsl-registry-scoped-members-01.txt > Status: > https://datatracker.ietf.org/doc/draft-romijn-grow-rpsl-registry-scoped-members/ > HTMLized: > https://datatracker.ietf.org/doc/html/draft-romijn-grow-rpsl-registry-scoped-members > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-romijn-grow-rpsl-registry-scoped-members-01 > > Abstract: > > This document updates RFC2622 and RFC4012 by specifying src-members, > a new attribute on as-set and route-set objects in the Routing Policy > Specification Language (RPSL). This attribute allows a specific > registry to be defined for each member in a set, avoiding problematic > ambiguity when resolving set members. A new validation rule allows > gradual upgrades and backwards compatibility. > > > > The IETF Secretariat > >
_______________________________________________ GROW mailing list -- grow@ietf.org To unsubscribe send an email to grow-le...@ietf.org
