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

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

16 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

Re: [db-wg] Draft Agenda RIPE76 - Database Working Group
by William Sylvester 26 Apr '18

26 Apr '18

Dear all, Below is the agenda for the Database Working Group for RIPE76. If you have any questions, comments, or requested changes please let the chairs know. Best regards, William & Denis DB-WG Chairs A. Introduction - 5 min * Welcome * Scribe * Jabber * Agenda B. Operational Update RIPE Database - 20 mins Tim Bruijnzeels, RIPE NCC C. Current State of RDAP - 20 mins Andrew Newton, ARIN D. General Data Protection Regulation (GDPR) - 10 mins Maria Stafyla, RIPE NCC E. A modern chatbot approach for accessing RIPE database - 10 mins Laurenz Wagner, Janus Cloud F. NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation - 5 mins G. NWI - Open Proposals - 10 mins Z. AOB (open discussion)

1 0

Draft Agenda RIPE75 - Database Working Group
by William Sylvester 17 Apr '18

17 Apr '18

Dear all, Below is the draft outline for the Database Working Group agenda for RIPE76. If you have any questions, comments, or requested changes please let the chairs know. Best regards, William & Denis DB-WG Chairs A. Introduction - 5 min * Welcome * Scribe * Jabber * Agenda B. Operational Update RIPE Database - 40 mins Tim Bruijnzeels, RIPE NCC C. NWI - Open Proposals - 10 mins D. General Data Protection Regulation (GDPR) - 10 mins Maria Stafyla, RIPE NCC Z. AOB (open discussion)

1 0

Updating the database via HTTP API - best practices
by Alexander Stranzky 12 Apr '18

12 Apr '18

> What is the current best practice for handling Auth on HTTP API updates to the RIPE database, and is there a roadmap for change that I can consider as I write my tools to publish and maintain objects? Same situation here on my end. Anyways, I'd love to have an authentication method that uses one of my existing RIPE DB key-cert objects (maybe something like an HMAC). Cheers, Alex -- velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * D-63452 Hanau Geschäftsführer: Franz G. Köhler, Arek Akilli * AG Hanau * HRB 7588 Tel: +49 6181 1898119 * http://www.velia.net Follow us on twitter: https://twitter.com/velia_net

1 0

Updating the database via HTTP API - best practices
by Andy Davidson 11 Apr '18

11 Apr '18

Hi, I would like to publish information in the RIPE database based on what my single-source-of-truth configuration management system knows and not what I sort of remember when I kind of get around to updating RIPE. Fortunately, there is a splendid looking API for this. The most recent and complete documentation that I can find with support from a search engine is https://github.com/RIPE-NCC/whois/wiki/WHOIS-REST-API. On the subject of Authentication, the document says: "Currently only passwords are supported to authenticate updates”. Is this still up to date and entirely true? Does it mean MD5 password or does this mean I should be able to use something based on my SSO authentication pair to generate a password field? I thought that MD5 had been deprecated in circa. 2015? https://www.ripe.net/ripe/mail/archives/db-wg/2015-June/004666.html What is the current best practice for handling Auth on HTTP API updates to the RIPE database, and is there a roadmap for change that I can consider as I write my tools to publish and maintain objects? Thanks for your help, database-wg & NCC experts, Andy -- Andy Davidson Asteroid International BV https://www.asteroidhq.com @asteroidhq @andyd -------------------------------------------------- Local interconnection. Where you need it.

1 0

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