This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] Abuse Contact Information - Policy Proposal
- Previous message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
- Next message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Fri Jul 23 15:32:29 CEST 2010
Dear Florian, This is an issue that was raised by the lawyers to the RIPE Data Protection Task Force. After consideration by the Task Force a recommendation was put to the RIPE Database Working Group. There is a reference to this in the RIPE NCC presentation to the RIPE 59 meeting in Lisbon http://www.ripe.net/ripe/meetings/ripe-59/archives.php?day=thursday The bulk access daily split files still make available all the operational data. If, after processing that data, you need the personal data for a specific object you can query the RIPE Database for that object and return the personal data or just the references to it. With the current design of the RIPE Database there is no way to have any opt in methods for personal data. The RIPE NCC has no relationship with most of the people referenced by PERSON objects. RPSL does not provide any means of distinguishing between PERSON objects for network administrators and PERSON objects related to end user customer data. Nor does it provide any means to gather, verify and store such opt in approval. Regards Denis Walker Business Analyst RIPE NCC Database Group Florian Weimer wrote: > * Denis Walker: > > >> Just to clarify this point, the RIPE NCC has no plans to shut down bulk >> access to operational data. The only restrictions are regarding personal >> and security data. There will be no bulk access to PERSON, ROLE, >> ORGANISATION or MNTNER objects. In other objects types NIC Handle >> references will also be removed from the bulk access data. >> > > NIC handles are operational data for many of us who need to contact > operators to address issues we encounter and make the Internet a > better place for everyone. > > I'm disappointed that RIPE NCC plans to take things into that > direction. Was this project prompted by requests from the membership? > > At the very least, you could introduce an opt-in flag so that we can > agree to have our data published in bulk form, so that we can benefit > from others willing to help us to keep our networks clean. > >
- Previous message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
- Next message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]