This proposal suggests to have the minimum assignment size for PI assignments to be a /24 when routing is a major issue for a multihoming End User.
This is a proposal for the RIPE NCC to regularly contact all current RIPE Database object holders with resources in the RIPE Database to ask them to actively check that all their details are up-to-date.
To actively check details, the object owner has to log into the LIR Portal and acknowledge the accuracy of data in their object(s) or update all existing objects if needed. The update date will be shown in the "changed:" attribute of every single object.
RIPE whois database data accuracy has been a big issue for years now. There have been several approaches to get better data accuracy within whois information all over the world.
There are two main reasons for data inaccuracy:
A secondary problem is data incompleteness:
ARIN conducts an annual POC (point of contact) validation process:
APNIC is currently discussing a similar approach:
If the current APNIC and RIPE NCC proposals are successful, the author plans to submit a similar proposal for the AfriNIC and LACNIC regions.
The proposal mentions a webform to report invalid database information. As an example, see the APNIC webform:
A link to the webform shall be linked in all RIPE Database output for reporting invalid contact information.
a. Arguments supporting the proposal
b. Arguments opposing the proposal