March 2018 - db-wg - mailman.ripe.net

<auto-dbm@ripe.net> is slow this afternoon.
by RIPE Database Administration 17 May '18

17 May '18

Dear Colleagues, Because of a very high level of use this afternoon, the response time of <auto-dbm(a)ripe.net> is longer than normal. I have made contact with those who are responsible and I expect the situation to improve as the machine works through the queue. Please be patient. Obviously we at the RIPE NCC Database Group are continuously working to make the performance of the database as good as possible. However, we cannot make improvements in zero time. We thank you for your co-operation up to now and we ask for your continued co-operation so that everyone receives the best possible service. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

2 2

Getting fraudulent entries removed
by Brian Rak 07 Apr '18

07 Apr '18

Hi, We've run into an issue where an unknown malicious party appears to have hijacked some of our IP space. They created entries in the RIPE database that they are using to actually get this space announced. What's even worse is their carrier is trying to say these announcements are legitimate because they have IRR entries (which is a whole other issue) What is the process like for actually getting this fraudulent entry removed? I've been in contact with RIPE NCC Support, and they have been super unhelpful (ref case #14523) The fraudulent entry is: https://apps.db.ripe.net/search/lookup.html?source=ripe&key=198.13.32.0/19A… route: 198.13.32.0/19 descr: 2nd route origin: AS39967 mnt-by: ADMASTER-MNT created: 2017-10-13T00:20:08Z last-modified: 2017-10-13T00:20:08Z source: RIPE I should also note that this ASN suspiciously appears to be announcing other people's space as well, but I can only confirm that this particular entry does not belong. I would suspect that their other IRR entries are fake as well. You can verify my request by reaching out to any of the POCs associated with this network: https://whois.arin.net/rest/net/NET-198-13-32-0-1 Thanks, Brian Rak

6 13

Getting 'responsible organization' out of RDAP
by Brian Rak 22 Mar '18

22 Mar '18

I've been attempting to use RDAP to verify our customer's IP information, however I'm running into some difficulties due to differences between ARIN's implementation and RIPE's. For example, I'm trying to get the organization name for a particular IP. On ARIN, this is easy. I look through the provided vcards for one where the kind is 'org', and that gives me the information about the organization. (ex: https://rdap.arin.net/registry/ip/66.55.158.27 ) With RIPE's RDAP implementation, this data does not seem to be readily available. For example, if I look at https://rdap.db.ripe.net/ip/195.66.225.160 I'd expect to find the string 'London Internet Exchange Ltd.' somewhere within the response. If I look at the web UI: https://apps.db.ripe.net/db-web-ui/#/query?searchtext=195.66.225.160#result… , this information is easily available. Would it be possible to expand the RDAP results to include organization information? This seems like it would just be another vcard entry, so there really shouldn't be any backwards compatibility issues. Apologies if this isn't the correct list, I can't really find any information about RDAP on RIPE's website.

3 6

Whois Update Server Migration
by Edward Shryane 22 Mar '18

22 Mar '18

Dear Working Group, on Wednesday 21st March, we plan to migrate the Whois Update Server to a new configuration. This will cause a short downtime for Whois updates. Queries will not be affected. We will also create a Service Announcement on the RIPE NCC website. Regards, Ed Shryane RIPE NCC

2 4

Whois release 1.91 in Release Candidate environment, production release planned for 7th March
by Edward Shryane 14 Mar '18

14 Mar '18

Dear Working Group, RIPE Database release 1.91 has been deployed to the Release Candidate environment. If no issues are found, we plan to deploy to production on 7th March. Release 1.91 includes the following main changes : - Removed "abuse-mailbox:" attribute from person,mntner,organisation,irt object types (as part of NWI-7 abuse-c implementation) - Don't allow multiple spaces, tab characters, or multiple lines, in the organisation org-name attribute. - Exclude certain email addresses (such as mailing lists and ticket queues) in abuse-mailbox,e-mail,irt-nfy,mnt-nfy,notify,ref-nfy,upd-to attributes - Added "end of stream" comment to NRTM responses - Fixed inconsistent newlines in --list-versions response The complete list of changes in this release can be found in GitHub: https://github.com/RIPE-NCC/whois/blob/master/changes.txt Please let us know if you see any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC

1 2

New on RIPE Labs: Legal Grounds for Lawful Personal Data Processing and the RIPE Database (GDPR)
by Athina Fragkouli 06 Mar '18

06 Mar '18

Dear all, In our third article on the GDPR, we are looking at the legal basis for processing personal data in the RIPE Database when it refers to an individual resource holder or contact person. We will also outline the relevant obligations of the responsible parties. https://labs.ripe.net/Members/Athina/gdpr-legal-grounds-for-lawful-personal… Kind regards, Athina Fragkouli Head of Legal RIPE NCC

1 0