June 2019 - db-wg - mailman.ripe.net

GDPR and the RIPE Database
by Edward Shryane 08 Oct '19

08 Oct '19

Dear Working Group, as mentioned in last week's DB-WG meeting, we will shortly be implementing the following changes: - Do not include personal data in historical queries (notify, e-mail, address attributes). - Do not include person/role references in historical queries (admin-c, tech-c, ping-hdl, zone-c). A legal review found we should not return historical contact details, as they may contain personal data, which is not in line with the purpose of the RIPE database or data protection legislation. For background, Maria Stafyla from RIPE NCC Legal presented on this topic at RIPE 76: https://ripe76.ripe.net/presentations/101-GDPR-Database-WG-RIPE-76.pdf Regards Ed Shryane RIPE NCC

4 8

Extending Unreferenced Object Cleanup
by Edward Shryane 21 Aug '19

21 Aug '19

Dear Working Group, as presented at last week's DB-WG meeting, I'd like to extend the current Unreferenced Object Cleanup: https://www.ripe.net/manage-ips-and-asns/db/support/clean-up-of-unreference… which deletes the following unreferenced objects after 90 days: - organisation, mntner, person, role objects - mntner - person/role pairs to also delete the following groups of unreferenced objects after 90 days: - mntner - organisation pairs - organisation - person/role pairs - mntner - person/role - organisation groups This change affects a small number of objects in the database, but is consistent with the goal of removing unnecessary data. Please give me your feedback on this proposal, in particular if there are operational reasons to retain this data. Regards Ed Shryane RIPE NCC

4 4

Whois Release 1.94.1
by Edward Shryane 08 Jul '19

08 Jul '19

Dear Working Group, RIPE Database release 1.94.1 has been deployed to the Release Candidate environment. This is a bug-fix release, with no new features. If no issues are found, we plan to deploy to production on Monday, 8th July. This release contains two main changes: - Consistent substitution of invalid latin-1 characters (e.g. control characters) and non-latin-1 characters across all Whois Update APIs (e.g. Syncupdates, Mailupdates, REST API). Following this release, we will also cleanup existing objects to be consistent. - Improvements to the RDAP protocol implementation (https://rdap.db.ripe.net). For a full list of changes, refer to the release notes: https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-rel… More information on the Release Candidate environment can be found on our website: https://www.ripe.net/manage-ips-and-asns/db/release-notes/rc-release-candid… Please let us know if you find any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC

1 1

--list-versions
by Ronald F. Guilmette 26 Jun '19

26 Jun '19

I am having some trouble applying the --list-versions option to some things that are either (a) the first IPv4 address of an inetnum: object and/or (b) a netname: object. Is this option even supposed to work on such things? Examples: --list-versions 194.162.0.0 --list-versions DE-ECOTEL-950515 I am having serious trouble understanding why this isn't working. If someone could explain, I'd appreciate it. Regards, rfg P.S. Yes, I am aware already that --list-versions and --show-version options do not work on person & role objects.

5 7

Whois Release Process
by Cynthia Revström 24 Jun '19

24 Jun '19

Hello DB-WG, Ed proposed a change to the WHOIS release process at the DB-WG session @ RIPE78. This change would be to immediately deploy bug fixes without a release candidate. I would just like to voice my opinion on it, so my thought is that maybe give the db-wg 24h to voice opinions or something like that. Just a thought but anyways. - Cynthia

4 5

RIPE Database Questionnaire
by Sandra Bras 05 Jun '19

05 Jun '19

Hello everyone, As a follow-up to my short presentation in the RIPE Database Working Group session during RIPE 78, I would like to share the link to our questionnaire. We’re currently developing the RIPE Database exam for the RIPE NCC Certified Professionals programme. It is crucial that we align not only our learning content, but also the exam questions, with the tasks you regularly carry out in the RIPE Database. It is important for us that, as an experienced user of the RIPE Database, you help us ensure that our testing is robust and relevant, by completing this short questionnaire (only four questions): https://www.ripe.net/support/certified-professionals/ripe-database-question… <https://www.ripe.net/support/certified-professionals/ripe-database-question…> Read more about the RIPE NCC Certified Professionals programme in this RIPE Labs article: https://labs.ripe.net/Members/sandra_bras/ripe-ncc-certified-professionals-… <https://labs.ripe.net/Members/sandra_bras/ripe-ncc-certified-professionals-…> And sign up to take part in the pilot RIPE Database exam and become one of our first RIPE NCC Certified Professionals: https://www.ripe.net/support/certified-professionals <https://www.ripe.net/support/certified-professionals> Please do contact me if you would like any further information. Warm regards, Sandra Brás E-Learning Programme Manager RIPE NCC

2 1

Authenticating References to Objects
by Edward Shryane 04 Jun '19

04 Jun '19

Dear Working Group, as mentioned at last week's DB-WG meeting, I'd like to propose extending authenticating references to other objects. Currently, only references to organisation objects can be protected with the mnt-ref attribute. However, we could extend this protection to other types of objects: - Abuse-c role - Technical contact, admin contact, zone contact etc. (person/role) - Organisation maintainer(s) This would prevent unauthorised references to an organisation's objects (e.g. to impersonate a third party or mis-direct abuse email). Please let me know your feedback on this proposal. Regards Ed Shryane RIPE NCC

8 10