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/db-wg@ripe.net/
[db-wg] RIPE Bulk WHOIS change anonymization
- Previous message (by thread): [db-wg] RIPE Bulk WHOIS change anonymization
- Next message (by thread): [db-wg] RIPE Bulk WHOIS change anonymization
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Tue Jun 17 15:57:46 CEST 2014
On Tue, Jun 17, 2014 at 03:22:56PM +0200, Micha wrote: > I asked your DB Managers and they suggested to forward my question to you. > I hope that I don't unnecessarily spam you, but I couldn't find this > in your db-wg archive with a quick look. > > Question: > Is it possible to keep the actual "date" of the "changed:" line > unanonymized? > By now it's always: changed: unread at ripe.net 20000101 > I get that you want to protect personal data like the mail adresses > in this field, but I can't see how this date could harm anyone. > > I would like to use this date field for research purpose and I am > happy about your answers! A proposal has been circulating through db-wg to create two new attributes which are accurate and reliable and deprecate the "changed:" attribute, I believe this covers what you want to research in the database: http://www.ripe.net/ripe/mail/archives/db-wg/2014-May/004362.html Kind regards, Job
- Previous message (by thread): [db-wg] RIPE Bulk WHOIS change anonymization
- Next message (by thread): [db-wg] RIPE Bulk WHOIS change anonymization
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]