- db-wg - mailman.ripe.net

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

RIPE NCC to stop enforcing accurate organisation names in "descr:" attribute
by Tim Bruijnzeels 26 Feb '15

26 Feb '15

Dear colleagues, The "org:" attribute now provides a consistent way to find the organisation for all resources in the RIPE Database. The RIPE NCC is planning to stop enforcing the organisation name in the "descr:" attribute for those resources allocated or assigned by it. There was a time when the "org:" attribute was not mandatory for INETNUM, INET6NUM and AUT-NUM objects. And to make it clear which organisation is the holder of a resource, the RIPE NCC has been enforcing that the first "descr:" line of these objects reflects the organisation name for resources that are allocated or assigned by the RIPE NCC. But this limit was never enforced on resources not allocated or assigned by the RIPE NCC, such as sub-assignments and legacy resources. Nowadays these object types do have a mandatory "org:" attribute, and today the RIPE NCC also enforces that the organisation referenced here, and its name, reflect the registry records for these resources. For resources not allocated or assigned by the RIPE NCC it's the responsibility of resource holders to ensure that the referenced organisation accurately reflects the holder of e.g. sub-assignments and legacy resources. Please let us know if you have any comments. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC

4 4

RIPE Database Release 1.78 Deployed to Release Candidate Environment
by Tim Bruijnzeels 23 Feb '15

23 Feb '15

Dear colleagues, The RIPE NCC is pleased to announce the deployment of RIPE Database software release 1.78 to the Release Candidate (RC) environment. Please note that the previous release candidate, 1.77, was rolled back because of an issue with concurrent updates that only became apparent in the production environment. Release 1.78 includes a fix for this issue. Extensive automated tests have been added to prevent similar issues from happening again. This release includes all features and fixes from release 1.77. In addition, release 1.78 of the RIPE Database software also includes a number of other improvements: = We added a dry-run option for the REST API = We improved the error message when creating an organisation object without and AUTO primary key = Fix for Issue #286: Pending create route requests are not removed when the route is created Detailed release notes are published on the web site: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.78 We invite all users of the RIPE Database to review the new release in the RC environment: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-envir… Please let us know if you find any issues. We plan to deploy this release to the production environment on Monday 23 February. We look forward to any questions or comments you might have. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC

1 1

[training] RIPE NCC Training Courses April-June 2015
by Training Services 17 Feb '15

17 Feb '15

Dear colleagues, Our training team travels the RIPE NCC service region to deliver training courses to our members without any additional cost. Over the next few months, we'll be in Tashkent, Lisbon, Poznan, Belgrade, Manchester, Kuwait, Helsinki, Dublin, Nicosia, Kazan, Amsterdam, Vienna, Hamburg. Visit the following page to register and to check which training courses we are giving in your area: https://lirportal.ripe.net/training/courses The RIPE NCC delivers the following training courses: - Local Internet Registry (LIR) Training Course - RIPE Database Training Course - Basic IPv6 Training Course - Advanced IPv6 Training Course - Routing Security Training Course - DNSSEC Training Course For more information visit: http://www.ripe.net/lir-services/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0

[training] RIPE NCC Training Courses April-June 2015
by Training Services 17 Feb '15

17 Feb '15

Dear Colleagues, Our training team travels the RIPE NCC service region to deliver training courses to our members without any additional cost. Over the next few months, we'll be in Tashkent, Lisbon, Poznan, Belgrade, Manchester, Kuwait, Helsinki, Dublin, Nicosia, Kazan, Amsterdam, Vienna, Hamburg. Visit the following page to register and to check which training courses we are giving in your area: https://lirportal.ripe.net/training/courses The RIPE NCC delivers the following training courses: - Local Internet Registry (LIR) Training Course - RIPE Database Training Course - Basic IPv6 Training Course - Advanced IPv6 Training Course - Routing Security Training Course - DNSSEC Training Course For more information visit: http://www.ripe.net/lir-services/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0

Implementation plan for replacing "changed:" with "last-modified:" and "created:" published
by Tim Bruijnzeels 02 Feb '15

02 Feb '15

Dear colleagues, The RIPE Database Working Group requested the RIPE NCC to replace the “changed:” attribute in the RIPE Database with “created:” and “last-modified:”. Following discussions at RIPE 69, the RIPE NCC has met with the working group chairs and finalised an implementation plan consisting of three phases: 1) introduce the new attributes “created:” and “last-modified:” 2) make the "changed:" attribute optional 3) deprecate the "changed:" attribute. The time lines and documentation for each phase are detailed here: https://labs.ripe.net/Members/tim/deprecating-the-changed-attribute-in-the-… We look forward to any questions or comments you might have. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC

2 3

[training] RIPE NCC Webinars - new dates
by Training Services 02 Feb '15

02 Feb '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

RIPE DB updates service disruption
by Theodoros Polychniatis 29 Jan '15

29 Jan '15

Dear Colleagues, A short downtime for RIPE DB Updates is necessary today, between 14:00 - 15:00 CET, to apply an urgent security patch. The downtime for updates will be a few minutes and queries will not be affected. We apologise for the short notice and thank you for your understanding. Kind regards, Theodoros Polychniatis, Software Engineer, RIPE NCC

1 0

Reporting un-assigned but used ip-space
by Arnd Vehling 29 Jan '15

29 Jan '15

Hello, today i recognized a spambot attack from "62.122.74.100" which lies in an un-assigned ip-range. How to correctly report this? cheers, Arnd

2 1

RIPE Database Release 1.77 Deployed to Release Candidate Environment
by Tim Bruijnzeels 26 Jan '15

26 Jan '15

Dear colleagues, The RIPE NCC is pleased to announce the deployment of RIPE Database software release 1.77 to the Release Candidate (RC) environment. This release includes: = Business rules to support the 2012-07 policy = A clear banner in the Release Candidate (RC) and Training web tools = Internal code to support resiliency improvements = Fixes for four infrequently occurring bugs This release also includes the bug fix released earlier in 1.76.1: = Incorrectly formatted blank lines in updates were crashing the NRTM service (issue #284) This release does not introduce any major functional changes. Detailed release notes are published on the web site: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.77 We invite all users of the RIPE Database to review the new release in the RC environment: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-envir… Please let us know if you find any issues. We plan to deploy this release to the production environment on Monday 26 January. We look forward to any questions or comments you might have. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC

1 1