March 2015 - db-wg - mailman.ripe.net

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

17 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

History lost ...
by Erik Bais 21 May '15

21 May '15

Hi, With the IP transfers going in full swing, it is quite common these days that the larger prefix size is broken up in to multiple smaller prefixes.. As the original prefix is split up, the IPRAs remove the original prefix from the database .. and with it .. the history Is there a way to preserve that data to be able to still lookup the data using list-versions or show-version # Regards, Erik Bais

13 24

Database release 1.79 deployed to RC environment
by Tim Bruijnzeels 07 May '15

07 May '15

Dear colleagues, The RIPE NCC is pleased to announce the deployment of RIPE Database software release 1.79 to the Release Candidate (RC) environment: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-envir… <https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-envir…> This release introduces the new attributes "created:" and "last-modified:" as part of the first phase of the deprecating the changed attribute in the RIPE Database. You can find more information about the three phases of this effort here: https://labs.ripe.net/Members/tim/deprecating-the-changed-attribute-in-the-… <https://labs.ripe.net/Members/tim/deprecating-the-changed-attribute-in-the-…> It should be noted however that: = The new attributes will only be enabled in output this Thursday 2 April (because updating all objects with initial values takes a long time) = We have found that we needed to use the 1970-01-01T00:00:00Z instead of 0000-00-00T00:00:00Z (because it's invalid, and we observed inconsistencies in dealing with year 0 AD different libraries) We will update the referenced article shortly to reflect these changes. This release also changes attribute "referral-by" from mandatory to optional. This attribute is part of a mntner object for historical reasons and will be deprecated. Detailed release notes are published here: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.79 <https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.79> Documentation for this release is published here: https://www.ripe.net/data-tools/support/documentation/ripe-database-documen… <https://www.ripe.net/data-tools/support/documentation/ripe-database-documen…> Please let us know if you find any issues with this release. We plan to deploy this release to the production environment on Tuesday 28 April, and we plan to enable the new "created:" and "last-modified:" attributes the following Monday 4 May - after the initial values have been added for all objects. Please let us know if you have any questions or comments. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC

5 12

[training] RIPE NCC Webinars - new dates
by Training Services 30 Mar '15

30 Mar '15

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

Call for agenda items DB-WG meeting during RIPE70, Amsterdam, NL
by Job Snijders 23 Mar '15

23 Mar '15

Dear DB-WG participants, We are reaching out to you for agenda items for the Database Working Group session during the RIPE70 meeting in Amsterdam, Netherlands 11-15 May 2015. Some of the current topics are: - 'source:' differentiation - RIPE-NCC-RPSL-MNT - UTF-8 in the DB - cross-registry authorisation - updates from RIPE NCC - .... your topic? Please submit your items or topic suggestions to the chairs directly or to the list for public discussion. Soon we'll publish a draft agenda, waste no day if you want microphone time! :-) The Database Working Group session is scheduled Thursday 14 May, from 16:00 till 17:30. Looking forward to a successful session and see you soon in the beautiful city of Amsterdam! Kind regards, Job, Piotr & Nigel

1 0

RIPE NCC to remove mnt-lower RIPE-NCC-END-MNT from ASSIGNED PI objects
by Tim Bruijnzeels 06 Mar '15

06 Mar '15

Dear colleagues, Sub-assignments of ASSIGNED PI objects are technically possibly in the RIPE Database, but not allowed by RIPE policy. And to prevent that such sub-assignments are created, the RIPE NCC has been including "mnt-lower: RIPE-NCC-END-MNT" on ASSIGNED PI Objects. Nowadays however we prefer to enforce such policy restrictions by the use of special "business rules" and a rule has already been implemented for this particular case. Therefore the RIPE NCC would like to do a bulk change on all ASSIGNED PI objects in the RIPE Database and remove "mnt-lower: RIPE-NCC-END-MNT" where it's present. Since we feel that this operation does not significantly alter the affected objects we plan to suppress sending out notify messages regarding this change, and we will make sure that this change is excluded when the "last-modified:" attribute is added in future. Please let us know if you have any questions or comments. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC

4 5

Monthly open-items summary
by Nigel Titley 02 Mar '15

02 Mar '15

Folks, The WG chairs have decided that a monthly "open-items" list might be useful to the WG. I'm doing the first and it will then rotate around the other chairs on a monthly basis. - "source: field for non RIPE address space", this proposal needs to be reworked to accommodate the large transfer of route objects from RIPE to the new AFRINIC DB - "restrict usage of RIPE-NCC-RPSL-MNT" we need to continue this discussion and request action from RIPE NCC - proposal for latin1 primary keys, utf8 allowed in user modifiable data - cross routing registry authorisation. This is a long term project which will ultimately allow authorisation between registries and will allow de-duplication of data across the registry system as a whole. This will be progressed as a BOF at RIPE 70 meeting if possible. - continue promotion of the the new Afrinic RR If I've missed anything please let me know. Nigel

1 0