Hello,

James and I have submitted new versions of our two related RPSL drafts: 
draft-ietf-grow-rpsl-registry-scoped-members-01 and 
draft-bensley-rpsl-exclude-members-01. These had expired, but we are still 
actively working on this.

The registry-scoped-members draft has several smaller updates, with 
clarifications on comments in auto-generated data, leaving aut-num policy out 
of scope, and an option to disable filtering.

The exclude-members draft has substantial refactoring for clarity and brevity, 
an option to disable filtering, clarified handling of members that are both 
included and excluded, and clear rules for route-set/prefix range operator 
handling.

Both drafts are now Standards Track rather than Informational, and I joined as 
a co-author on exclude-members.

Ongoing: working out some complexities around uniqueness across registries and 
practicalities when operators edit objects with auto-generated content. You can 
see our work on this in the respective GitHub repositories. There are also 
still other rough edges in the text.

Next, I will implement this in IRRDv4, and we'll suggest implementation in RIPE 
Database, the other major IRR server, RIPE db-wg. So far feedback there has 
been very positive. Along with implementation, we will create tests for forward 
and backward compatibility across mixes of old/new objects, parsers and 
servers, and document the results.

We welcome any comments and suggestions.

Sasha

https://datatracker.ietf.org/doc/draft-ietf-grow-rpsl-registry-scoped-members/
https://datatracker.ietf.org/doc/draft-bensley-rpsl-exclude-members/
https://github.com/mxsasha/rpsl-registry-scoped-members
https://github.com/jwbensley/rpsl-exclude-members

_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to