- db-wg - mailman.ripe.net

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

Historical data and deleted objects
by Bengt Gördén 28 Nov '13

28 Nov '13

Hi, We had some talk about historical data on RIPE67 and I think we agreed on the possibility of retrieving deleted history too. Is there any progress on this? regards, -- Bengt Gördén Resilans AB

3 3

New minor release 1.70.1 to fix replication issue
by Johan Åhlén 21 Nov '13

21 Nov '13

Dear colleagues, We have identified the cause of the recent replication issues we've been experiencing with the MySQL back-end. In short, we have detected a bug in the particular MySQL version we are currently running. In order to avoid this bug, we had to implement a workaround that we deployed today at 16:30 (UTC +1). Since the workaround was the only feasible solution, we were forced to build and deploy a new minor version (1.70.1) of the RIPE Database software. Release notes can be found here: https://www.ripe.net/data-tools/db/release-notes Kind regards, Johan Åhlén Assistant Manager, Database RIPE NCC

1 0

Problem with replication
by Johan Åhlén 21 Nov '13

21 Nov '13

Dear colleagues, Since 0:00 (UTC+1) on Wednesday, 20 November, we’ve experienced some issues with data replication in our back-end system. This has led to unreasonable delays between executing a database update and seeing the result in the queries in some cases. We want to ensure you that all updates have been processed and no data has been lost. We have a temporary fix to restore data replication to a normal state, so currently the replication is working as it should. However, for unknown reasons, the replication has been failing at some point during the night. We’re working very hard to identify the root cause of this issue in order to find a permanent solution to the problem. Please check the Service and Security Announcements page for updates if you encounter any issues: http://www.ripe.net/lir-services/service-announcements. Kind regards, Johan Åhlén Assistant Manager, Database RIPE NCC

1 0

[training] RIPE NCC Training Courses January-March 2014
by Training Team 18 Nov '13

18 Nov '13

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 Lisbon, Frankfurt, Busto Arsizio, Manamah, St. Petersburg, Tallinn, London, Warsaw, Copenhagen, Amsterdam, Bucharest. 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: - LIR Training Course - Database Training Course - IPv6 for LIRs Training Course - Routing Security 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

RIPE Database Release 1.70
by Denis Walker 12 Nov '13

12 Nov '13

Dear colleagues, The new release 1.70 of the RIPE Database was deployed to the TEST Database environment on Thursday, 31 October 2013 and is now ready to be deployed to the production database. The deployment will commence at 20:00 (UTC+1) on Thursday, 14 November 2013 and may take up to three hours to complete. During this time, updates will not be available. Any email updates submitted during this period will be queued. Updates by any other means will return an error message. Queries will not be affected during this deployment. The reason for the outage is an operational clean-up that the RIPE NCC has to do occasionally on the RIPE Database. Some long-since deprecated objects and attributes will be removed from the SQL table structure. This clean-up will not cause any visible change to users. The clean-up was done on the TEST Database during the deployment of 1.70 in October. Regards Denis Walker Business Analyst RIPE NCC Database Team

1 0

RIPE Database Release 1.70 Available
by Denis Walker 06 Nov '13

06 Nov '13

Dear colleagues, The RIPE NCC is pleased to announce that we will deploy a new release of the RIPE Database to the TEST Database environment on Thursday, 31 October 2013. The release is scheduled for production deployment on Thursday, 12 November 2013. Detailed information about the new release, including dates and information about the changes, can be found at: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.70 Of special note in this release is the inclusion of "pending route authentication". This is an alternative and simplified way of authorising route object creation. Two separate updates for a single route/route6 object are treated as one create request. This has no impact on users who still submit a complete route object with all authorisations included. If you have any questions or comments, we look forward to hearing them. Regards, Denis Walker Business Analyst RIPE NCC Database Team

1 1

[training] RIPE NCC Webinars - new dates
by Training Team 29 Oct '13

29 Oct '13

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

Support for recursive expansion of as-set to a list of ASNs
by Job Snijders 21 Oct '13

21 Oct '13

Dear DB-WG, Now that the new database backend is in place, this should allow for awesome features such as server sided recursion of AS-SETs into a list of ASNs. Implementing IRRd's !i flag will prevent a lot of back and forth communication between whois server and client to provide the client with a full list of ASNs which are part of an AS-SET. Clients such as bgpq3 support this flag. I've filed an enhancement request on github: https://github.com/RIPE-NCC/whois/issues/72 But we could use this thread to assess community support and gather a sense of priority. Kind regards, Job

3 2

abuse-c + org / inetnum
by Gilles Massen 19 Oct '13

19 Oct '13

Dear WGs, In the light of the upcoming RIPE meeting I'd like to bring the problem of a single entity (organisation) wanting different abuse-c for different resources up again. The discussion starting in June (http://www.ripe.net/ripe/mail/archives/db-wg/2013-June/004079.html ) was rather open ended. Apparently the only workable solution at this point is to create a duplicate organisation object with a different abuse-c. Is data duplication really the solution that the WGs would like? Gilles -- Fondation RESTENA - DNS-LU 6, rue Coudenhove-Kalergi L-1359 Luxembourg tel: (+352) 424409 fax: (+352) 422473

6 6

Route Polict Verification
by Alexander Azimov 17 Oct '13

17 Oct '13

Dear colleagues, During current RIPE meeting I have presented my report about verification of route policy from registries with deeper analysis for RIPE database. I analysed the customer to provider relations because of its global visibility. The result are fearful: 60% of link completeness, less than half of this amount have information about Pref values and again most of pref values have errors. As a result there is only 10% likelihood to find real priorities using this dataset. The community must decide how to change this situation. In my opinion there are only two ways to overcome this problem: verify this data or delete at all. All our data is available on our website <http://radar.qrator.net>. The collected data is based on imitation mathematical model with use of AS paths recovered from BGP views and novel active verification abilities that could detect priorities on every level of BGP decision making process. We are eager for collaboration and eager to help RIPE Stats or RIPE DB to verify policy data, highlight errors and give other aggregated data if community decides that it is needed. -- | Alexander Azimov | HLL l QRATOR | tel.: +7 499 241 81 92 | mob.: +7 915 360 08 86 | skype: mitradir | mailto: aa(a)highloadlab.com | visit: www.qrator.net

4 6

Korrektion: RIPE67 DB-WG Draft Agenda V2
by Wilfried Woeber 16 Oct '13

16 Oct '13

..."of course" I go it wrong, my sincere apologies: [1] for remote participation: this is *08:00 UTC* Oh my, blush, Wilfried

1 0

RIPE67 DB-WG Draft Agenda V2
by Wilfried Woeber 16 Oct '13

16 Oct '13

Dear DB-WG folks, Chairpersons, "Meeting"! This is the 2nd draft of an agenda for the DB-WG Meeting at RIPE67 in Athens, scheduled for October 17, 2013. For time slot allocations please refer to the most up-to-date meeting plan at https://ripe67.ripe.net/programme/meeting-plan/ The DB-WG Meeting is scheduled for *Thursday*, starting at 11:00 local time[1] in the morning. The length of our timeslot is 90 Minutes. The overall (draft) RIPE 67 meeting outline is already available at https://ripe67.ripe.net/programme/meeting-plan/ Changes from V1: - the separate items pertaining to the DataBase are lumped together - a new item on GeoLoc Data Management Please feel free to propose additional topics to be discussed! I'd also suggest that you submit your points of view regarding the topics on the proposed agenda on the mailing list, preferably before the WG meeting's start :-) Best regards, hope to see you soon in Athens, Wilfried. [1] for remote participation: this 09:00 UTC ________________________________________________________________________ A. Administrative Matters . Welcome . select scribe . finalise agenda . approval of minutes from previous WG meeting(s) . review of action list B. Data Base Update (Denis.W., Johan.Å., RIPE NCC) - operational report - software release management and TEST DB - things "in the pipe" - WEIRDS C. UTF-8 transparency in the Registry - functionality and/or restrictions by components - policy or business logic interactions, - coordination /input with/from other WGs D. Common Format for GeoLoc data (Zoltan Sz., Google) Y. Input from other Working Groups and/or Task Forces - review of abuse contact stuff (N.N. t.b.c.)) Z. AOB ________________________________________________________________________ 16.10.2013 11:20 UTC

1 0

[training] RIPE NCC Webinars - new dates
by Training Team 15 Oct '13

15 Oct '13

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://lirportal.ripe.net/training/courses 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

Improvements to RIPE Database Software Release Management
by Johan Åhlén 10 Oct '13

10 Oct '13

Dear colleagues, Following recent discussion regarding the release management of the RIPE Database software, we looked closely at our procedures and would like to propose some improvements. Together with the Database Working Group chairs, we've scheduled an informal meeting during RIPE 67, open for anyone that is interested in this topic, to discuss the proposals and talk about how we can improve our procedures. The meeting will take place on Monday, 14 October from 18:00-19:00 in room Sigma + Theta. We hope you will join us. Of course, you can also send your feedback and suggestions to this list. This is what we propose: - Split the RIPE Database software into smaller modules. Modularisation would minimise the release frequency for our services. For instance, with a modern API like RDAP we might have bi-weekly major releases and weekly minor releases to quickly respond to changes in the specification. With the NRTM feed, there might be just one major release per year or even less. - Replace the "emergency release" with a "minor release" that only contains patches for operational purposes and bug fixes. No new functionality would be introduced and no feature changes. We would also have "major releases" where functionality is added, changed or removed. With major releases we would keep the minimum two-week user test period leading up to the production release as stated in the previously proposed release procedure. With any minor release, we would put it in production as soon as it's available. Most bugs affect some users. Rather than trying to determine urgency based on numbers of users, size of users, number of networks affected, importance of functionality affected, etc., we would treat all bugs the same. In short, if someone reports an issue to us, we fix it right away. This process has generally worked well over recent years. - Improve the test environment. We know that users would like to have their real data to do proper testing. To solve this issue, we propose to use snapshots of the current database for this purpose. - Improve communication surrounding new releases. This covers all documentation and how we inform users about changes. We hope that you find this way forward beneficial. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

2 2

Syntax Change to Aut-num Object in the RIPE Database
by Denis Walker 09 Oct '13

09 Oct '13

Dear colleagues, We would like to give you a heads-up about a proposal, currently being considered, to add two new attributes to the aut-num object in the RIPE Database: "import-via:" and "export-via:". In this email we are not concerned with the details of this specific change so much as the fact that a change is being considered. We know that these objects are very important for routing and many of them are updated daily in the RIPE Database. We also know that many scripts exist for auto-generating these objects and processing the contents. Although the RFC for RPSL clearly states that scripts should be written to ignore attributes they don't recognise, we don't know if all scripts are written this way. The RIPE NCC is considering the best ways to get information about any changes to routing object syntax in the RIPE Database out to the people who need to know. We would welcome any feedback on this issue from the community. Regards, Denis Walker Business Analyst RIPE NCC Database Team

1 0

Re: [db-wg] new "via" attributes in aut-num Class
by Erik Bais 09 Oct '13

09 Oct '13

Hi Job & Johan, I think the implementation makes sense and my compliments on the draft. It looks good: > http://tools.ietf.org/html/draft-snijders-rpsl-via Is this already in the new db version or is this still waiting for more community support ? For me, support +1. Kind regards, Erik Bais A2B Internet > > I have submitted the following draft to the IETF: > > http://tools.ietf.org/html/draft-snijders-rpsl-via > > And I have submitted a patch for the RIPE whois server to support the feature. > > https://github.com/job/whois > > The extension should be backward compatible with minimal impact on existing > tools and processes, following Section 10.2 of RFC2622. RPSL parsers which > do not understand the new attributes are expected to just ignore it. > > I am looking for feedback from this community, and especially the community's > blessing to allow RIPE NCC to adopt the patch. > > Kind regards, > > Job

2 1