- db-wg - mailman.ripe.net

[training] RIPE NCC Webinars - new dates
by Training Services 11 Feb '14

11 Feb '14

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

Multiple Sources and the REST API?
by Aleksi Suhonen 07 Feb '14

07 Feb '14

Hello, I'm trying to fetch data from the RIPE db and the mirrored databases at the same time: http://rest.db.ripe.net/search?source=ripe&source=apnic&inverse-attribute=o… I get 400 Bad Request even tho it should work according to the documentation I'm reading: https://github.com/RIPE-NCC/whois/wiki/WHOIS-REST-API-search Halp. -- +358 4567 02048 / http://www.trex.fi/ Aleksi Suhonen / TREX Regional Exchanges Oy You say "potato", I say "closest-exit."

2 1

New minor release 1.71.1 to fix REST API JSON issue
by Denis Walker 06 Feb '14

06 Feb '14

Dear colleagues, We have identified the cause of the REST API JSON issues some users have been experiencing. Details can be found on github: https://github.com/RIPE-NCC/whois/issues/114 We deployed a new minor version (1.71.1) of the RIPE Database software today at 17:15 (UTC +1) to fix this issue. Release notes can be found here: https://www.ripe.net/data-tools/db/release-notes Regards, Denis Walker Business Analyst RIPE NCC Database Team

3 4

RC version of the JSON API?
by Job Snijders 06 Feb '14

06 Feb '14

Hi, I want to use the JSON API RC edition of the database in an automated fashion to detect changes that break our software earlier. But I have trouble finding the correct endpoint. For production I use the following URL: https://apps.db.ripe.net/whois What is the equivalent URL for the RC version of the database? From the post on http://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-enviro… it is not clear which of the URLs would emulate apps.db.ripe.net/whois. I tried: rc.db.ripe.net/whois rest-rc.db.ripe.net/whois whois-rc.ripe.net/whois I kinda expect rest-rc.db.ripe.net/whois to work, but it gives me a "The requested URL /whois/create was not found on this server." error. What is the endpoint? Kind regards, Job

2 1

Release 1.71.1 reverted, current RIPE Database release is 1.71
by Johan Åhlén 06 Feb '14

06 Feb '14

Dear colleagues, Earlier today we deployed a minor release of the RIPE Database software. The release contained a correction of an invalid data structure returned in the JSON format. The issue is described in detail here: https://github.com/RIPE-NCC/whois/issues/114 The beta REST API was decommissioned with the deployment of 1.71. As the issue above was affecting users that had not yet migrated to the new API we decided to go ahead with the minor release. However, we were just informed that there are users that rely on this specific structure for their operations so we have reverted the minor release. The current RIPE Database version in production is now back to 1.71 We’ve also made sure that the old beta API is available for any users that can’t migrate because of the issue mentioned above. Please contact me directly and I will provide you with the details on how you can connect to the old beta API. We are sorry for any inconvenience this might have caused you and if you have any questions or concerns then please let me know. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

1 0

RIPE Database Release 1.71
by Johan Åhlén 04 Feb '14

04 Feb '14

Dear colleagues, We are pleased to announce RIPE Database release 1.71. You can find details about the new features, changes and how you might be affected, and important dates in the release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.71 The new release contains the "import-via" and "export-via" attributes that were discussed in the Database and Routing Working Groups at RIPE 67, the initial implementation of which was made by Job Snijders. After further discussions on the mailing lists, the working group chairs decided that this feature should be incorporated in the RIPE Database. You can find out more about these attributes here: http://www.ietf.org/id/draft-snijders-rpsl-via-02.txt With this release we would also like to introduce our new Release Candidate environment. The Release Candidate environment is distinct from the TEST Database, and aims to provide an environment as close as possible to "production" where you can test that your software will work with upcoming RIPE Database releases. You can find out more about the Release Candidate environment in the release notes linked above. We look forward to hearing any questions or comments you might have! Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

2 2

Proposed Implementation Plan for 2012-08, "Publication of Sponsoring LIR for Independent Number Resources"
by Johan Åhlén 30 Jan '14

30 Jan '14

Dear colleagues, Last week, the RIPE community reached consensus on the policy proposal 2012-08, "Publication of Sponsoring LIR for Independent Number Resources”. The RIPE NCC’s proposed implementation plan of the policy can be found here: https://labs.ripe.net/Members/johan_ahlen/policy-2012-08-proposed-plan-for-… You can find the full policy proposal at: https://www.ripe.net/ripe/policies/proposals/2012-08 The corresponding RIPE Document is ripe-603, which is available at: https://www.ripe.net/ripe/docs/ripe-603 If you have any comments or concerns, please let us know. Note: this email has been sent to both the RIPE NCC Services WG and the RIPE Database WG mailing lists. We would like to ask you to keep the discussion on the RIPE NCC Services WG mailing list to better facilitate participation. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 20 Jan '14

20 Jan '14

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

[training] RIPE NCC Webinars - new dates
by Training Services 06 Jan '14

06 Jan '14

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

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