December 2013 - 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

Draft minutes of RIPE 67 meeting
by Nigel Titley 05 Nov '14

05 Nov '14

Please find draft minutes of the DB-WG meeting held in Athens today. Comments, complaint, misrepresentations etc, to me Nigel

1 1

Support for expansion of an origin into a list of prefixes
by Job Snijders 01 May '14

01 May '14

Dear RIPE DB-WG, Much like my previous request regarding server side expansion of objects, I'd very much like the RIPE Database team to implement two flags which IRRd currently supports: !g & !6 I've filed an enhancement request on github: https://github.com/RIPE-NCC/whois/issues/73 The !g and !6 flags signficantly reduce the amount of RPSL interpretation a client has to perform, as the server provides the clients with a straight answer (abeit simplified). If the DB team implements such a feature, I'd also very much like an implementation in context or RDAP so I can query for lists of prefixes through HTTP rather than WHOIS. Kind regards, Job

2 1

Re: [db-wg] [routing-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
by Job Snijders 12 Dec '13

12 Dec '13

Dear people, On Thu, Oct 24, 2013 at 03:05:21PM +0200, Denis Walker wrote: > During the RIPE 67 Meeting in Athens last week, there was some > discussion about the introduction of new "via" attributes to the > AUT-NUM object. This issue has been discussed on both the Database and Routing Working Group mailing lists and at RIPE 67 in both Database and Routing sessions. Overall there was support for it on the Database Working Group list. On the routing-wg@ mailinglist one comment was made, also in support of the introduction of these attributes. The software is ready to be deployed, but the RIPE NCC needs someone to say 'yes, go ahead' if there is consensus. Does anyone have a problem with moving forward towards deployment? Bullet point pitch: - The change is backwards compatible with older RPSL parsers. - The new attributes are completely optional. - This change adds advanced functionality that will especially benefit route server operators and participants. Kind regards, Job

4 5