- db-wg - mailman.ripe.net

Re: [db-wg] WG Chair Selection - Call for Discussion
by William Sylvester 05 Oct '18

05 Oct '18

WG Members, Congratulations to everyone on the success of NWI-5! With the deployment behind us and everyone back from holiday in August we are moving to the next step in our chair selection process. This email opens the two (2) weeks of chair selection discussion. All members of the community are encourage to make a discussion and express their approval or otherwise of the presented candidates. The candidates are as follows and have either made their interest known on this mailing list, or directly to the chair(s). I encourage each candidate to reiterate their qualifications to the mailing list. Piotr Strzyzewski Sean Stuart As members of this working group please discuss your approval or otherwise of each candidate. Best regards, Denis & William DB-WG Chairs

4 3

"key-cert" objects - emails listed as "owner" even thou id has been revoked
by netravnen＠gmail.com 03 Oct '18

03 Oct '18

Hi db-wg, Was updating my key-cert object in the database. And was wondering if it is by design revoked key id's is listed as owner of the key? (I would normally expect revoked id's not being listed inside key-cert objects.) The Explanation =============== I have several gpg id's as part of the key. Half is active. Half is revoked id's. All id's; even the revoked ones; is being listed as "owner:" when viewing the key-cert object in the database. -Netravnen

2 1

alloclist.txt
by nusenu 01 Oct '18

01 Oct '18

Hi, before I start parsing the alloclist.txt [1] file (with multiline context) I was wondering if there is a more parse-friendly version of that? (one record per line?) thanks, nusenu [1] https://ftp.ripe.net/pub/stats/ripencc/membership/alloclist.txt -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

2 2

RIPE Policy Proposal 2018-05 Aims to Publish Legal Address Information
by Marco Schmidt 27 Sep '18

27 Sep '18

Dear colleagues, We just published the RIPE Policy proposal, 2018-05, "Publication of Legal Address of Internet Number Resource Holder", to the RIPE NCC Services Group mailing list. The goal of the proposal is for the RIPE NCC to publish the validated legal address information of holders of Internet number resources. As the publishing of such data likely will happen in the RIPE Database, we want to notify the Database Working Group. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-05 We encourage you to review this proposal and send your comments to <ncc-services-wg(a)ripe.net> before 26 October 2018. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

Re: [db-wg] Draft Agenda RIPE77 - Database Working Group
by William Sylvester 25 Sep '18

25 Sep '18

Dear Working Group Members, Below is the DRAFT agenda for the Database Working Group for RIPE77. If you would like to present please submit your content as soon as possible to the chairs. 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 – 45 mins Edward Shryane, RIPE NCC C. Discussion: PERSON objects in the RIPE Database – 15 mins Denis Walker D. NWI - Open Proposals – 15 mins Z. AOB (open discussion)

1 0

PERSON objects in the RIPE Database
by Alexander Stranzky 21 Sep '18

21 Sep '18

On 20/09/2018 15:04, denis walker via db-wg wrote: > Colleagues, > > I will start with a blunt question, then give some arguments for my > concern. In May the RIPE NCC told me there are?more than 2 million > PERSON objects in the RIPE Database. That is almost 25% of the objects > in the database. Who are these people and why do we hold so much > personal data? Hello, I suspect that many of these objects are old (pre-API) and/or duplicates. Before RIPE had a REST API (and I can't tell how many ISPs still use emails to create their resources) automatically fetching, linking, and updating a RIPE object was a pain (as is the current situation with APNIC) and likely involved someone to create the email personally. Hence going the easy route--making new entries every time. Regards, Alexander Stranzky -- velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * 63452 Hanau Geschäftsführer: Franz G. Köhler, Arek Akilli * AG Hanau * HRB 7588 Tel: +49 6181 1898119 * http://www.velia.net

5 7

Re: [db-wg] PERSON objects in the RIPE Database
by Cynthia Revström 20 Sep '18

20 Sep '18

Hi, I am not sure how the best way to do this but maybe check the database for person handles with identical name, address, phone number and such things. Also maybe if we could take a look at the amount of person handles that are not used at all in any other object, and potentially delete them. Kind regards, Cynthia Revström On 2018-09-20 14:57, Alexander Stranzky via db-wg wrote: > On 20/09/2018 15:04, denis walker via db-wg wrote: >> Colleagues, >> >> I will start with a blunt question, then give some arguments for my >> concern. In May the RIPE NCC told me there are?more than 2 million >> PERSON objects in the RIPE Database. That is almost 25% of the objects >> in the database. Who are these people and why do we hold so much >> personal data? > Hello, > > I suspect that many of these objects are old (pre-API) and/or > duplicates. Before RIPE had a REST API (and I can't tell how many ISPs > still use emails to create their resources) automatically fetching, > linking, and updating a RIPE object was a pain (as is the current > situation with APNIC) and likely involved someone to create the email > personally. Hence going the easy route--making new entries every time. > > Regards, > Alexander Stranzky >

2 1

Whois release 1.92.6 deployed to Production
by Edward Shryane 20 Sep '18

20 Sep '18

Dear Working Group, we have deployed a bug-fix release 1.92.6 to production that fixes a bug when updating an object with a lowercase source value (e.g. "source: ripe"). The release notes have been updated: https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-rel… Regards Ed Shryane RIPE NCC

1 0

avoiding RIPE IRR vs. RPKI ROA mismatches/inconsistencies
by nusenu 14 Sep '18

14 Sep '18

Dear DB Working Group, when looking into RPKI and RIPE IRR coverage I stumbled on prefixes that are covered by a RIPE route object and a RPKI ROA, which is great, but there are cases where these records make conflicting statements about the origin of a prefix. example: 185.46.20.0/22 origin according to ROA: AS199785 origin according to route object: AS61952 origin according to RIS: AS61952 (matches route object) Note: this is just an example to better illustrate the issue. (I didn't do a comprehensive analysis to be able to tell how often this is the case but for a sample of ~1900 prefixes I found 3 such occurrences.) Since route objects and ROAs are created by the prefix holders this is possible (human mistake). Are there any measures in place to prevent or at least warn about the inconsistency when the IP holder creates/updates route objects and ROAs that would result in inconsistencies? What do you think about an UI feature that says something like: "You are about to change/create the route object for prefix ... would you also like to update the existing ROA to match the route object and help avoid inconsistencies?" [ ] yes [ ] no, I know what I'm doing, I'll fix the mismatch manually similarly for updating/creating ROAs. Should there even be a 'No' option? Should the question even be exposed to the user or should records simply be synced automatically once one of either is changed by the IP holder? and simply showing an info like: "We took care of updating your ROA/route object to keep in sync." In case there are well established best practices for an ASN change of a prefix these best practices should be incorporated (i.e. delete the route object and ROA, change the actual announcement in BGP, create new route and ROAs that match the announcement) kind regards, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

2 3

Whois release 1.92.5 deployed to Production
by Edward Shryane 11 Sep '18

11 Sep '18

Dear Working Group, after deploying the NWI-5 changes last week, we found an issue preventing out of region transfers (the top-level placeholder template still referenced the RPSL maintainer). We have now deployed a bug-fix release 1.92.5 to production that fixes this issue. Regards Ed Shryane RIPE NCC

1 0