<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> </head> <body dir="auto"> <div dir="auto">denis wrote:</div> <div dir="auto">> This defeats your own argument. You were arguing you need to know the<br> > addresses of these natural persons so you can link separate resources<br> > having the same address. Using the IDs of random people and drunks<br> > from a bar will give them all different addresses. Knowing these<br> > addresses doesn't help you in any way.</div> <div dir="auto"><br> </div> <div dir="auto">Maybe they would use the address of the bar where they met the drunkard? :)</div> <div dir="auto"><br> </div> <div dir="auto">Having many persons registered with that address. Or even multiple registrations whose addresses all match with pubs in Y area, would certainly be an interesting pattern worth to be discovered.</div> <div dir="auto"><br> </div> <div dir="auto">Or even just a pattern of addresses not existing in that city or with no buildings.</div> <div dir="auto"><br> </div> <div dir="auto">Sadly, filters designed to block obvious fake data will generally only lead malicious actors to produce better lies, not to provide their real details.</div> <div dir="auto"><br> </div> <div dir="auto"><br> </div> <div dir="auto"><br> </div> <div dir="auto">In a previous mail you mentioned:</div> <div dir="auto">> When these people apply to be a member I am sure the RIPE NCC requires proof of identity and proof of address. </div> <div dir="auto"><br> </div> <div dir="auto">but -being slightly more skeptic- I would like to know what kind of address verification is performed.</div> <div dir="auto"><br> </div> <div dir="auto">Document ripe-770 do mention the first part:</div> <div dir="auto">"Each agreement signed with either the RIPE NCC or with a sponsoring LIR must be accompanied by <strong>supporting</strong> <strong>documentation</strong> proving the existence (and validity) of the legal or natural person (see below)."</div> <div dir="auto"><br> </div> <div dir="auto">but no mention is made of verifying the physical address.</div> <div dir="auto">https://www.ripe.net/publications/docs/ripe-770#111</div> <div dir="auto"><br> </div> <div dir="auto"><br> </div> <div dir="auto">As for the identity proof, it suggests</div> <div dir="auto">"Valid identification documents (e.g., identification card, passport)"</div> <div dir="auto"><br> </div> <div dir="auto">I guess one might go to RIPE NCC office to show them their passport and assert that they do exist and match it. That's probably the most secure way of verification. But I doubt many people would do that (maybe, during the assembly...).</div> <div dir="auto"><br> </div> <div dir="auto">Sending the passport or id card to RIPE NCC would not be be acceptable. The exact way to do that is not described there, but the model agreement says "the End User shall include a photocopy of a valid identity card." and I suspect that's what will be done on almist every case.</div> <div dir="auto"><br> </div> <div dir="auto">https://www.ripe.net/manage-ips-and-asns/resource-management/number-resources/independent-resources/independent-assignment-request-and-maintenance-agreement</div> <div dir="auto"><br> </div> <div dir="auto">Obviously, someone who tricked another one (drunk or not) into getting a copy of their id card could easily fulfill this requisite.</div> <div dir="auto"><br> </div> <div dir="auto"><br> </div> <div dir="auto">Maybe those on this list that are resource holders could tell us if their physical address was ever validated by RIPE in any way?</div> <div dir="auto"><br> </div> <div dir="auto">Regards</div> <div dir="auto"><br> </div> <div dir="auto"><br> -- <br> INCIBE-CERT - Spanish National CSIRT<br> https://www.incibe-cert.es/<br> <br> PGP keys: https://www.incibe-cert.es/en/what-is-incibe-cert/pgp-public-keys<br> <br> ====================================================================<br> <br> INCIBE-CERT is the Spanish National CSIRT designated for citizens,<br> private law entities, other entities not included in the subjective<br> scope of application of the "Ley 40/2015, de 1 de octubre, de Régimen<br> Jurídico del Sector Público", as well as digital service providers,<br> operators of essential services and critical operators under the terms<br> of the "Real Decreto-ley 12/2018, de 7 de septiembre, de seguridad de<br> las redes y sistemas de información" that transposes the Directive (EU)<br> 2016/1148 of the European Parliament and of the Council of 6 July 2016<br> concerning measures for a high common level of security of network and<br> information systems across the Union.<br> <br> ====================================================================<br> <br> In compliance with the General Data Protection Regulation of the EU<br> (Regulation EU 2016/679, of 27 April 2016) we inform you that your<br> personal and corporate data (as well as those included in attached<br> documents); and e-mail address, may be included in our records <br> for the purpose derived from legal, contractual or pre-contractual<br> obligations or in order to respond to your queries. You may exercise<br> your rights of access, correction, cancellation, portability,<br> limitationof processing and opposition under the terms established by<br> current legislation and free of charge by sending an e-mail to<br> dpd@incibe.es. The Data Controller is S.M.E. Instituto Nacional de<br> Ciberseguridad de España, M.P., S.A. More information is available<br> on our website: https://www.incibe.es/proteccion-datos-personales<br> and https://www.incibe.es/registro-actividad.<br> <br> ====================================================================<br> </div> <div><br> </div> </body> </html>