- db-wg - mailman.ripe.net

comment on comment at mic: database "purpose" vs not-globally-routed prefixes
by Sandra Murphy 17 May '18

17 May '18

(Sorry about this. typed the comment into the chat window, hit submit, got “disconnected” error, reconnected, but too late to comment.) The comment at the mic was that there are many IP prefix resources in the database that are not globally routed, and that those objects were not part of the RIPE database purpose as stated. So collection of personal data for those objects could not rely on the RIPE database purpose for justification. I disagree that the lack of current global routing for an IP prefix means the RIPE database purpose of facilitating coordination does not apply. An allocated prefix can be globally announced at any time. So there’s a need to have the data, anyway. In the current state of routing security, an allocated prefix can be globally announced at any time, not necessarily by the legitimate prefix holder. We’ve seen several examples of some ISP announcing a prefix that seemed not to be in use, sometimes even registering a route object for the announcement, and using that prefix for some unfriendly purpose. So there is still a need to have contact data for a prefix even before the legitimate prefix holder decides to globally announce the prefix. —Sandy

2 1

FW: Weird IRR entry
by Gunnar Guðvarðarson 17 May '18

17 May '18

Yeah, there is also a corresponding ASn aut-num: AS10 as-name: EJU1-RIPE admin-c: EJU1-RIPE tech-c: EJU2-RIPE status: OTHER mnt-by: EJU created: 2018-02-18T06:19:45Z last-modified: 2018-02-18T06:19:45Z source: RIPE AS10 is allocated to ARIN, and is in use by CSNET: as-block: AS8 - AS27 descr: ASN block not managed by the RIPE NCC I reported these objects to ripe-dbm, ops and abuse @ripe.net

1 0

<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

New on RIPE Labs: The GDPR: Amendments to the RIPE Database
by Mirjam Kuehne 14 May '18

14 May '18

Dear colleagues, This is our fourth in a series of RIPE Labs articles discussing the General Data Protection Regulation (GDPR) implementation. Here we're looking at amendments that will be needed to the RIPE Database in order to ensure GDPR compliance: https://labs.ripe.net/Members/maria_stafyla/how-were-implementing-the-gdpr-… Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: Out-of-Region ROUTE(6) and AUT-NUM Objects in the RIPE Database
by Antony Gollan 09 May '18

09 May '18

Dear colleagues, In a new article on RIPE Labs, Denis Walker provides some context around the changes being made to the way out-of-region objects are managed and represented in the RIPE Database: https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objec… Kind regards, Antony Gollan RIPE NCC

2 1

Re: [db-wg] RIPE database on ftp.ripe.net
by Paul Weiss 08 May '18

08 May '18

Hi Marten, In the directory https://ftp.ripe.net/ripe/dbase/split/ <https://ftp.ripe.net/ripe/dbase/split/> there are lots of "splits", is there an inventory guide so that we can understand which type of data each split contains? We need to access and search for; Company name, Org.number, Country, City, IP-range Can we also ftp download the complete IP Databases per country in Europe? Thanks, Paul Weiss

2 1

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