Thanks for publishing this proposal.
I don't see how this proposal solves the issues it claims it is introduced to solve. It rather seems to guarantee that information in the database will increasingly become stale.
To break it down by rationale:
"One of the main reasons for registering IPv4 PA assignments was that
LIRs could show their use of IPv4 and thus justify the request for an
additional IPv4 allocation from the RIPE NCC. However, this requirement
has become obsolete since the RIPE NCC ran out of IPv4 addresses in
2019."
This merely means that this particular reason is no longer relevant for IPv4 addresses.
"The application of IPv4 assignment registration policies in the RIPE
Database is inconsistent. Some resource holders flood the database with
tiny assignments (e.g. assignments for individual IP addresses), while
many others do not register any assignments."
This proposal does nothing to resolve the perceived database inconsistency, there is no proposed cleanup of current database entries.
"This proposal is in line with the data consistency and data minimisation principles (as defined in the DBTF report
[3]:
- Data stored in the RIPE Database should be adequate, relevant, and limited to only what is necessary.
- It is recommended that resource registration requirements are applied consistently."
This proposal does not adequately describe this.
"Reduce the risk of LIRs registering personal data in the public database for no longer beneficial administrative/policy reasons."
This is a red herring. If this was the goal of a proposal, why not propose minimizing the amount of personal data, by e.g. restricting the use and publication of personal names and personal e-mail addresses?
"More flexibility: LIRs can choose for themselves which information they
think is necessary to document and which is not, making it easier to
adapt to different situations."
This appears to be the core and only real argument for the proposal.
As the proposal stands, I am against it.