Hi Leo On Wed, 1 Jun 2022 at 00:22, Leo Vegoda <leo@vegoda.org> wrote:
Hi,
On Tue, May 31, 2022 at 2:49 PM denis walker <ripedenis@gmail.com> wrote:
[...]
It would also be good to understand whether this issue relates to a tiny fraction of the registrations. What proportion of registrations and what proportion of the registered number resources are we discussing?
It is almost impossible to write a script to analyse this unless the script can recognise a natural person's name. But for a general idea I flicked through the INETNUM split file on the FTP site and can see a large number of names and addresses of people in the assignment objects.
As the RIPE NCC will have contracts in place, they should be able to tell us what proportion of LIRs are natural people. With that information we can start to understand whether this can be addressed purely through database rules or needs multiple approaches.
That might be interesting to know but unless the RIPE NCC's internal database has a flag to indicate a natural person they would have the same problem. But the numbers are not the real question. Anyone can see by flicking through the split file there is a 'significant' number of objects with full name and address details of people. And if one of them is you it is very significant. We also know there are people who won't become a resource holder or even get an assignment because of the risk of their personal details being entered into the RIPE Database. So we always come back to the fundamental question, for what purpose do we publish the name and address of a natural person who is a resource holder or who has an assignment from an LIR? We can also differentiate here between publishing the details and storing the details not for public access. If and when we establish the purpose of this information we can look at technical solutions. We should also keep in mind that this information is completely separate from being able to contact the operator of a network. So we are trying to establish why anyone needs to know who is responsible, accountable, liable for a block of IP addresses...and who needs to know that. Technical solutions may address how they can access this information. cheers denis proposal author
Kind regards,
Leo