Removal of specific records of personal contact information

To minimise annoyances to users and the membership we would like to proceed with the process in a timely manner.

With this goal in mind the RIPE NCC proposes the following process:

1. The following unreferenced person objects will be deleted:

   objects referenced only from .de domains, according to the list provided by DENIC (or list of mntners that define that set as obtained from the snapshot of the RIPE Database on the date of deletion of .de objects [June 2000]);

   Currently this list comprises the following maintainers (DENIC-P, XLINK-MNT, FREEDOMS, ROKA-P, DTAG-NIC, ECCE-NOC, KOMPLEX, ABCAG-MNT, ONE2ONE-MNT, A MADEE-RIPE-MNT, AS1849-MNT, OLEANE-NOC, WESPE-MNT, DREIMARK49-MNT, INTERNET-NOC, UUNET-P, NA CAMAR-NOC, SCHLUND-P, ROUTING-MNT, RAK-NET, BO-DOMREG, DNSNET-MNT, AS5617-MNT, AS2529-MNT, A S2871-MNT, PSINET-UK-SYSADMIN, ONNOW-MNT, DKNET-MNT, RAIN-TRANSPAC, NETTUNO, KNIPP-NOC-MNT, CSL-MNT, DFN-NTFY, TDK-MNT, VISCOMP-MNT, SL-CUS-MNT, ECORE-NET, HIGHSPEED-DOM, SPACENET-P, K DT-MNT, NLNET-MNT, WWW-MNT, PRHO-GUARDIAN, INX-MNT, KSD-MNT, MBT-MNT, NDH-P, EU-IBM-NIC-MNT2 , AS5427-MNT, ITNET-MNT, SEKTORNET-MNT, GLOBVILL-DOMREG, SECURE-NETZ, TRMD-MNT, SSERV-MNT, H OS-GUN, NETCOLOGNE-MNT, MAINT-AS3352, TELIANET-LIR, GLOBAL-MNT, COLT-FR-MNT, VHM-MNT, MNT-NE XTRA-DE, VIADE-MNT, MARIDAN-P, AS5378-MNT, PROFI-MNT, NACAMAR-RES, ADNS-MNT, LUACT-NOC, UBCO M-MNT, DE-VOSS, DATANET-NOC, ROM-MIKNET, IDNET-MNT, EDEX-MNT, ICMS-NOC-MAINTAINER, CNM-MNT, IVM-MNT, JIPPIIDE-MNT, SDT-NOC, NACAMAR-POP, OTENET-GR-MNT, NETD-MNT, WEBSPACE-SERVICE-DE, W EB4YOU-MNT, FR-EASYNET, ARCOR-MNT, ISAR-NIC, AS3233-MNT, INETC-MNT, WBC-NOC, POP-MNT, HOSTWE B-MNT, CNSPLUS-MNT, PEIM-MNT, EU-IBM-NIC-MNT, INETWIRE-MNT, MDA-Z, REGISTRIERT-MNT, ECGBR-MN T, HANSENET-NOC, EPCNET-MNT, ARNES-MNT, SIRECO, OMC1-RIPE-MNT, PING-MNT, AS8853-MNT, ODN-MNT , PLACE-MNT, COLT-P, BAIS-MNT, VCITIES-MNT, PTN-MNT).

   This list may be updated during the days up to the proposed date, dependent on data provided by DENIC to the RIPE NCC.
   Other ccTLDs have already initiated or completed similar processes.

2. any other person and role objects that do not have a mnt-by attribute and are unreferenced.
3. Individuals who have unreferenced and unmaintained (without a mnt-by attribute) person objects and want to protect their objects in the database should tag them with a special mntner (RIPE-NCC-PN-NONE-MNT). Simply add a mnt-by line pointing to this maintainer (mntner) to your unreferenced person object to indicate your personal desire to retain the data in the RIPE Database. Please refer to the text contained in the mentioned maintainer object for the terms of use.

   NOTE: If your person object already has a mnt-by line not listed above, you don't need to add RIPE-NCC-PN-NONE-MNT. It will not be deleted in this operation.

4. Due to the nature and the size of the data set involved, the RIPE NCC can not publish a list of all the objects affected. Interested individuals can verify the situation of their personal data by querying the RIPE Database with their usual whois client.
5. All of the object deletions will be performed in one step.
   Due to the amount of data processing involved, around 3 million objects, there will be an outage in updates for ~1 day. We plan to start the process Friday, 21 September 2001 in the evening and finish by the end of Saturday, 22 September 2001. More concrete details will be provided in the coming weeks.

Later steps may be necessary if after this bulk deletion, further analysis of the data in the RIPE Database shows the need for additional removals. The RIPE NCC shall discuss any further steps with the RIPE community.

For questions related to this process, send email to ripe-dbm@ripe.net