- db-wg - mailman.ripe.net

Re: [db-wg] NWI-7: abuse-c implementation plan
by Andreas Worbs 11 Jul '17

11 Jul '17

Yes, go ahead :) Am 11.07.17 um 09:02 schrieb denis walker via db-wg: -- Mit freundlichem Gruß Artfiles New Media GmbH Andreas Worbs Artfiles New Media GmbH | Zirkusweg 1 | 20359 Hamburg Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95 E-Mail: support(a)artfiles.de | Web: http://www.artfiles.de Geschäftsführer: Harald Oltmanns | Tim Evers Eingetragen im Handelsregister Hamburg - HRB 81478

1 0

Re: [db-wg] NWI-7: abuse-c implementation request
by Gert Doering 11 Jul '17

11 Jul '17

Hi, On Wed, Jun 28, 2017 at 01:56:49PM +0200, Tim Bruijnzeels via db-wg wrote: > Here is the RIPE NCC's impact analysis and proposed implementation plan for the changes to ???abuse-c:??? that the working group seeks. I think the proposed implementation makes sense, reducing overhead for maintaining the abuse contacts, while at the same time still giving a very clear order of precedence when querying -> works for me! Gert Doering -- long time LIR DB user -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279

1 0

Re: [db-wg] NWI-7: abuse-c implementation plan
by Piotr Strzyzewski 11 Jul '17

11 Jul '17

On Mon, Jul 10, 2017 at 07:37:37PM +0200, denis walker via db-wg wrote: Dear All > It is almost two weeks since Tim sent out a proposed implementation > plan and timeline. Can we assume no comments mean acceptance? If > anyone has any specific comments can we here them please. I see no reasons to wait for implementing the plan. Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski(a)polsl.pl

1 0

Re: [db-wg] NWI-7: abuse-c implementation plan
by Sebastian Wiesinger 11 Jul '17

11 Jul '17

> Colleagues > It is almost two weeks since Tim sent out a proposed implementation > plan and timeline. Can we assume no comments mean acceptance? If > anyone has any specific comments can we here them please. Hello, after two weeks of vacation I'm back and I support this implementation. Happy to see this topic come to conclusion this time! Regards Sebastian -- GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant

1 0

Re: [db-wg] NWI-7: abuse-c implementation plan
by denis walker 10 Jul '17

10 Jul '17

Colleagues It is almost two weeks since Tim sent out a proposed implementation plan and timeline. Can we assume no comments mean acceptance? If anyone has any specific comments can we here them please. Regardsdenisco-chair DB-WG From: Tim Bruijnzeels via db-wg <db-wg(a)ripe.net> To: William Sylvester <william.sylvester(a)addrex.net> Cc: DB-WG <db-wg(a)ripe.net> Sent: Wednesday, 28 June 2017, 13:57 Subject: Re: [db-wg] NWI-7: abuse-c implementation request Dear working group, Here is the RIPE NCC's impact analysis and proposed implementation plan for the changes to “abuse-c:” that the working group seeks. We expect that this will have a MEDIUM impact on the RIPE NCC. The RIPE Database Group Software team will have to implement changes, but because a clean-up of “abuse-mailbox:” is also in-scope of this proposal we also expect impact on our Customer Service department due to questions from users of the RIPE Database. We propose an implementation using the following phases: 1) Allow “abuse-c:” on INET(6)NUM and AUT-NUM objects We will deploy a new version of whois where the “abuse-c:” attribute will be allowed to exist on INET(6)NUM and AUT-NUM objects. The syntax will be the same as for the ORGANISATION object: abuse-c: [optional] [single] [inverse key] The Abuse Finder logic will be updated to use the first "abuse-c:" found in this order of priority: -the local "abuse-c:" in the resource object -the "abuse-c:" in an ORGANISATION object referenced by the "org:" attribute in the resource object -search up the resource object hierarchy (less specific objects) --the "abuse-c:" in the less specific resource object --the "abuse-c:" in an ORGANISATION object referenced by the "org:" attribute in the less specific resource object The search will stop when the top level resource object is reached. In addition to this we plan to introduce a business rule that will disallow “abuse-mailbox:” to be modified, or (re-)added to any object, other than ROLE objects. This will enable us to do a phased clean-up of this data without invalidating objects. 2) Clean up of “abuse-mailbox:” on ORGANISATION objects Three cases exist: A) “abuse-mailbox:” is present and it is the same as the “abuse-mailbox:” in the also present “abuse-c:” reference (8919 cases) In this case we propose to simply delete the “abuse-mailbox:” attribute and inform the holder. We will work on a clear text for this email, but the main message would be: "We removed “abuse-mailbox:” from your ORGANISATION object because this attribute is deprecated as the final step in the deployment of the "abuse-c:" attribute. However, we see that you were already using the preferred way to document abuse contact details for your organisation and you are referencing an “abuse-c:” ROLE object with the same email address in its its “abuse-mailbox:” attribute. No action is required.” B) “abuse-mailbox:” is present and it is different from the “abuse-mailbox:” in the also present “abuse-c:” reference (1848 cases) Note that some of these cases have been caused by the fact that since the introduction of “abuse-c:” LIRs can no longer modify the value of the “abuse-mailbox:” attribute. The intent was that “abuse-mailbox:” would have been cleaned up earlier, but unfortunately that dit not happen. That being said “abuse-c:” has been kept up to date by the LIR, and out of the two is also the one that is being shown on the Abuse Finder. Therefore we propose to delete the “abuse-mailbox:” attribute in these cases, and send a different notification to the holder with the following main message: "We removed “abuse-mailbox:” with value $email from your ORGANISATION object because this attribute is deprecated as the final step in the deployment of the "abuse-c:" attribute. However, we see that you were already using the preferred way to document abuse contact details for your organisation and you are referencing an “abuse-c:” ROLE object with that uses $email_2 in its “abuse-mailbox:” attribute. If the latter is correct no action is required. However if you want to modify the email address in your “abuse-c:” ROLE object, you can do so here (link to webupdates).” C) “abuse-mailbox:” is present, and there is no “abuse-c:” reference (28312 cases) We *could* create “abuse-c:” ROLE objects for these cases, using the same maintainers as the ORGANISATION object. However, the “abuse-mailbox:” attribute has not been shown in the Abuse Finder, and this change could lead to wrong or out-of-date addresses suddenly receiving abuse reports. Therefore we suggest that we delete the attribute instead, and send the following main message to the holder of the ORGANISATION object: "We removed “abuse-mailbox:” with value $email from your ORGANISATION object because this attribute is deprecated as the final step in the deployment of the "abuse-c:" attribute. However, if you wish to add an email address for abuse reports you can do so by editing your object here (link to web updates for the ORGANISATION object)." 3) Clean up of “abuse-mailbox:” on PERSON (89k cases), MNTNER (2500 cases) and IRT (238 cases) In these cases we propose to send a warning email to the holders of these objects with the following main message: “The “abuse-mailbox:” is deprecated on these object and will be removed in 4 weeks, if you want to set up abuse contact information on your resource objects you can do so by having a default “abuse-c:” on your ORGANISATION referenced by your resource objects, or possibly overriding that default with a specific “abuse-c:” reference on applicable resource objects." And then 4 weeks later we will preform the clean-up and refer back to this communication. 4) Clean up whois code Now that “abuse-mailbox:” only appears where it should, we will be able to update the whois code itself so that “abuse-mailbox:” is no longer syntactically allowed on objects other than ROLE objects. This will allow us to remove the business rule added in phase 1 and simplify the whois code and maintenance. We will also update the RIPE Database Documentation to reflect this. 5) Inverse queries As requested we can change the behaviour of the “pn” short cut to also search for “abuse-c:” in inverse queries. I.e. one can use: whois -r -i pn uk41-ripe Instead of: whois -r -i abuse-c,admin-c,tech-c,zone-c,author uk41-ripe Kind regards Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group > On 22 May 2017, at 20:56, William Sylvester via db-wg <db-wg(a)ripe.net> wrote: > > > From: William Sylvester <william.sylvester(a)addrex.net> > Subject: NWI-7: abuse-c implementation request > Date: 22 May 2017 at 19:59:44 GMT+2 > To: DB-WG <db-wg(a)ripe.net> > > > DB-WG Members, > > Support was shown for the proposal NWI-7 and no objections were raised after this round of discussion. At this time, the chairs request that the RIPE NCC schedule implementation of NWI-7 as described. > > This request is to add the "abuse-c:" attribute directly to the INET(6)NUM and AUT-NUM resource objects. The db-wg therefore ask the RIPE NCC to prepare an impact analysis, followed by an implementation plan and timeline for this request and the other issues raised in the problem statement of NWI-7 as follows: > > 1) Add the "abuse-c:" attribute to the INETNUM, INET6NUM and AUT-NUM objects > 2) Adjust the query logic to take account of 'local' "abuse-c:" attributes in preference to those referenced in ORGANISATION objects > 3) Allow both local and indirect references (via ORGANISATION objects) to "abuse-c:" attributes to operate hierarchically > 4) Deprecate "abuse-mailbox:" attribute from PERSON, ORGANISATION, MNTNER and IRT objects. > 5) Clean up data relating to the deprecated attributes. > 6) Update the 'person' keyword to take account of "abuse-c:" > > Thank you all for your work on this proposal! > > Kind regards, > > William > on behalf of DB-WG co-chairs > > >

1 0

New on RIPE Labs: Unifying the LIR Portal and RIPE Database User Experience
by Mirjam Kuehne 10 Jul '17

10 Jul '17

Dear colleagues, Over the years, the core services of the RIPE NCC, such as the LIR Portal and RIPE Database, have seen many changes. We are now going to unify the interfaces. Please find more details on RIPE Labs: https://labs.ripe.net/Members/AlexBand/unifying-the-lir-portal-and-ripe-dat… Kind regards, Mirjam Kühne RIPE NCC

1 0

Re: [db-wg] NWI-7: abuse-c implementation request
by Tim Bruijnzeels 28 Jun '17

28 Jun '17

Dear working group, Here is the RIPE NCC's impact analysis and proposed implementation plan for the changes to “abuse-c:” that the working group seeks. We expect that this will have a MEDIUM impact on the RIPE NCC. The RIPE Database Group Software team will have to implement changes, but because a clean-up of “abuse-mailbox:” is also in-scope of this proposal we also expect impact on our Customer Service department due to questions from users of the RIPE Database. We propose an implementation using the following phases: 1) Allow “abuse-c:” on INET(6)NUM and AUT-NUM objects We will deploy a new version of whois where the “abuse-c:” attribute will be allowed to exist on INET(6)NUM and AUT-NUM objects. The syntax will be the same as for the ORGANISATION object: abuse-c: [optional] [single] [inverse key] The Abuse Finder logic will be updated to use the first "abuse-c:" found in this order of priority: -the local "abuse-c:" in the resource object -the "abuse-c:" in an ORGANISATION object referenced by the "org:" attribute in the resource object -search up the resource object hierarchy (less specific objects) --the "abuse-c:" in the less specific resource object --the "abuse-c:" in an ORGANISATION object referenced by the "org:" attribute in the less specific resource object The search will stop when the top level resource object is reached. In addition to this we plan to introduce a business rule that will disallow “abuse-mailbox:” to be modified, or (re-)added to any object, other than ROLE objects. This will enable us to do a phased clean-up of this data without invalidating objects. 2) Clean up of “abuse-mailbox:” on ORGANISATION objects Three cases exist: A) “abuse-mailbox:” is present and it is the same as the “abuse-mailbox:” in the also present “abuse-c:” reference (8919 cases) In this case we propose to simply delete the “abuse-mailbox:” attribute and inform the holder. We will work on a clear text for this email, but the main message would be: "We removed “abuse-mailbox:” from your ORGANISATION object because this attribute is deprecated as the final step in the deployment of the "abuse-c:" attribute. However, we see that you were already using the preferred way to document abuse contact details for your organisation and you are referencing an “abuse-c:” ROLE object with the same email address in its its “abuse-mailbox:” attribute. No action is required.” B) “abuse-mailbox:” is present and it is different from the “abuse-mailbox:” in the also present “abuse-c:” reference (1848 cases) Note that some of these cases have been caused by the fact that since the introduction of “abuse-c:” LIRs can no longer modify the value of the “abuse-mailbox:” attribute. The intent was that “abuse-mailbox:” would have been cleaned up earlier, but unfortunately that dit not happen. That being said “abuse-c:” has been kept up to date by the LIR, and out of the two is also the one that is being shown on the Abuse Finder. Therefore we propose to delete the “abuse-mailbox:” attribute in these cases, and send a different notification to the holder with the following main message: "We removed “abuse-mailbox:” with value $email from your ORGANISATION object because this attribute is deprecated as the final step in the deployment of the "abuse-c:" attribute. However, we see that you were already using the preferred way to document abuse contact details for your organisation and you are referencing an “abuse-c:” ROLE object with that uses $email_2 in its “abuse-mailbox:” attribute. If the latter is correct no action is required. However if you want to modify the email address in your “abuse-c:” ROLE object, you can do so here (link to webupdates).” C) “abuse-mailbox:” is present, and there is no “abuse-c:” reference (28312 cases) We *could* create “abuse-c:” ROLE objects for these cases, using the same maintainers as the ORGANISATION object. However, the “abuse-mailbox:” attribute has not been shown in the Abuse Finder, and this change could lead to wrong or out-of-date addresses suddenly receiving abuse reports. Therefore we suggest that we delete the attribute instead, and send the following main message to the holder of the ORGANISATION object: "We removed “abuse-mailbox:” with value $email from your ORGANISATION object because this attribute is deprecated as the final step in the deployment of the "abuse-c:" attribute. However, if you wish to add an email address for abuse reports you can do so by editing your object here (link to web updates for the ORGANISATION object)." 3) Clean up of “abuse-mailbox:” on PERSON (89k cases), MNTNER (2500 cases) and IRT (238 cases) In these cases we propose to send a warning email to the holders of these objects with the following main message: “The “abuse-mailbox:” is deprecated on these object and will be removed in 4 weeks, if you want to set up abuse contact information on your resource objects you can do so by having a default “abuse-c:” on your ORGANISATION referenced by your resource objects, or possibly overriding that default with a specific “abuse-c:” reference on applicable resource objects." And then 4 weeks later we will preform the clean-up and refer back to this communication. 4) Clean up whois code Now that “abuse-mailbox:” only appears where it should, we will be able to update the whois code itself so that “abuse-mailbox:” is no longer syntactically allowed on objects other than ROLE objects. This will allow us to remove the business rule added in phase 1 and simplify the whois code and maintenance. We will also update the RIPE Database Documentation to reflect this. 5) Inverse queries As requested we can change the behaviour of the “pn” short cut to also search for “abuse-c:” in inverse queries. I.e. one can use: whois -r -i pn uk41-ripe Instead of: whois -r -i abuse-c,admin-c,tech-c,zone-c,author uk41-ripe Kind regards Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group > On 22 May 2017, at 20:56, William Sylvester via db-wg <db-wg(a)ripe.net> wrote: > > > From: William Sylvester <william.sylvester(a)addrex.net> > Subject: NWI-7: abuse-c implementation request > Date: 22 May 2017 at 19:59:44 GMT+2 > To: DB-WG <db-wg(a)ripe.net> > > > DB-WG Members, > > Support was shown for the proposal NWI-7 and no objections were raised after this round of discussion. At this time, the chairs request that the RIPE NCC schedule implementation of NWI-7 as described. > > This request is to add the "abuse-c:" attribute directly to the INET(6)NUM and AUT-NUM resource objects. The db-wg therefore ask the RIPE NCC to prepare an impact analysis, followed by an implementation plan and timeline for this request and the other issues raised in the problem statement of NWI-7 as follows: > > 1) Add the "abuse-c:" attribute to the INETNUM, INET6NUM and AUT-NUM objects > 2) Adjust the query logic to take account of 'local' "abuse-c:" attributes in preference to those referenced in ORGANISATION objects > 3) Allow both local and indirect references (via ORGANISATION objects) to "abuse-c:" attributes to operate hierarchically > 4) Deprecate "abuse-mailbox:" attribute from PERSON, ORGANISATION, MNTNER and IRT objects. > 5) Clean up data relating to the deprecated attributes. > 6) Update the 'person' keyword to take account of "abuse-c:" > > Thank you all for your work on this proposal! > > Kind regards, > > William > on behalf of DB-WG co-chairs > > >

1 0

Re: [db-wg] 2017 and RIPEdb only handles 700 updates per *MINUTE*
by Tim Bruijnzeels 21 Jun '17

21 Jun '17

Dear Working Group, The average update rate to the RIPE Database is 12 updates per minute. As shown the system is capable of handling a sustained rate of over 700 updates per minute for inetnums through mail updates without issues. That is 60 times the average rate. Cases where people actually need to do updates exceeding this rate are very few and far in between. This does not warrant allocating resources to improve this further - our efforts are better spent in other areas such as improving the usability of the user interface to help people manage their content better. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

1 0

Re: [db-wg] 2017 and RIPEdb only handles 700 updates per *MINUTE*
by Horváth Ágoston János 20 Jun '17

20 Jun '17

Hi Jeroen, I'm probably the most relevant person to asnwer your question right now, having been a core developer during the ripe database reimplementation project in 2013. We did that by running side by side with the old, C version of the ripe database software. As such, we were in no position to change the underlying database or its format. And guess what, the underlying database is coming from the previous server's reimplementation project, all the way from 2000. Reminds me of the story of the NASA booster rocket and the roman horse. There have been minor updates done over the years (like switching to innodb and sql transactions), the basics are still the same. Its data model is 100% optimized for query performance (since queries outnumber updates 100 to 1 or more). And most importantly, since updates (can and often do) have effect on one another, they are strictly serialized (as in, single-threaded). On top of that, all updates go through a rigorous rule checks before being accepted and taking effect. All this translates to that update performance. Note that the update performance is much higher for simple object types (say, person; my last knowledge was over 2000 objects/min), and very slow for complex ones (namely aut-num, with all the extra DNS checks). In practice, it was never an issue that a longer update ran for hours. This performance could be improved greatly given enough priority though. It was always a simple case of this requiring quite some dirty hack or major refactors, while this issue was always considered a minor nuisance, not enough to warrant either. BTW, if you look at the update graph you included, you see that updates are normally almost negligible compared to your batch. Thus most users of ripe database updates see very quick response times. I'd maintain that unless this really stops you from achieving your goals, it's probably best to leave the engineers work on deeper / more pressing issues. Like the fact that the RIPE DB actually needs a massive documentation and a day long training course even for basic usage. And even then, people are struggling with the weird object hierarchy and rules. While could be considered an acceptable approach in '99, this is way outdated by today's standards and user expectations. Cheers, Agoston On Tue, Jun 20, 2017 at 2:23 PM, Jeroen Massar via db-wg <db-wg(a)ripe.net> wrote: > > > ---------- Forwarded message ---------- > From: Jeroen Massar <jeroen(a)massar.ch> > To: db-wg(a)ripe.net > Cc: > Bcc: > Date: Tue, 20 Jun 2017 14:22:49 +0200 > Subject: 2017 and RIPEdb only handles 700 updates per *MINUTE* > https://www.ripe.net/analyse/statistics/ripe-database/ripedb-updates > > (see attached png for the current version as over time it will disappear) > > shows a nice peak with a max of 723.47 updates. > > Thus either the software is really bad, the updates are rate limited, or > the queries are so high that no further performance is to be expected. > > > As alluded to in the other thread, if there was less junk (those 400k > inet6nums for instance) then likely this would all scale better.... > > Are the RIPE DB-WG chairs still actively involved in the maintenance of > the RIPE Database!? > > As two of the co-chairs are working for RIPE NCC, are they able to tell > why such a process is slow and why these problems that are being raised > over and over on the various lists are not being resolved? > > Greets, > Jeroen >

1 0

Re: [db-wg] 2017 and RIPEdb only handles 700 updates per *MINUTE*
by denis walker 20 Jun '17

20 Jun '17

HI Jeroen The three DB-WG co-chairs (2 of whom are former RIPE NCC staff) are still actively involved in overseeing the maintenance of the RIPE Database. We don't have any 'hands on' involvement. Things may have changed a little since I was working on the RIPE Database so I am sure Tim will correct me if I am wrong here. Updates sent by email are queued and processed sequentially. It is a batch process, not real time as with Syncupdates or Webupdates. If you submit a single email with a huge number of objects, each of those objects are processed one at a time sequentially. If you submit several emails in quick succession with that huge list of updates spread over them, the emails will be queued and processed sequentially. Not sure now if there is only one queue or several for email updates. AFAIK the database can only update a single object at a time, no matter how many processors are running to feed updates to the database. The bottom line is, if you submit a huge number of objects to be updated it will take some time to complete. The number of daily queries massively outweighs the number of updates. So performance is naturally optimised to serve the query load. The average number of updates is easily handled, but when you get spikes it does slow down the update process for a while. The number of objects in the database makes no difference to performance on either queries or updates. So a large amount of junk will not affect performance. To address a couple of your points from your previous email. No one has ever defined what the "country:" attribute in an INET(6)NUM object means. It could be the location of the registries head office, their data centre, their service desk, their user base... It is not uncommon to see this value 'apparently' conflict with netname or address. If you believe 40% of the INET6NUM objects in the RIPE Database are junk, that is something the RIPE NCC Registration Services needs to comment on. cheersdenisco-chair DB-WG From: Jeroen Massar via db-wg <db-wg(a)ripe.net> To: db-wg(a)ripe.net Sent: Tuesday, 20 June 2017, 14:23 Subject: [db-wg] 2017 and RIPEdb only handles 700 updates per *MINUTE* https://www.ripe.net/analyse/statistics/ripe-database/ripedb-updates (see attached png for the current version as over time it will disappear) shows a nice peak with a max of 723.47 updates. Thus either the software is really bad, the updates are rate limited, or the queries are so high that no further performance is to be expected. As alluded to in the other thread, if there was less junk (those 400k inet6nums for instance) then likely this would all scale better.... Are the RIPE DB-WG chairs still actively involved in the maintenance of the RIPE Database!? As two of the co-chairs are working for RIPE NCC, are they able to tell why such a process is slow and why these problems that are being raised over and over on the various lists are not being resolved? Greets, Jeroen

1 0