- ncc-services-wg - mailman.ripe.net

Re: [ncc-services-wg] [db-wg] Urgent release of RIPE Database software
by Ruediger Volk, Deutsche Telekom Technik - FMED-41.. 15 Aug '13

15 Aug '13

Dear Johan, thanks a lot for the new much more transparent mode of software version management for the RIPE data base service. This is a huge improvement. Nevertheless I think that we need continued discussion in the community to improve mutual understanding of considerations and impact. Your message today brings up few consideratiosn from me (a bit more tuned to the general pro cess than the specific case). > We were recently made aware of some issues with the documentation > related to the REST API. To fix these issues requires a new release of > the Database software as some parts of the documentation are generated > from the active code. The documentation is vital for anyone wanting to > use the service. We therefore believe it is necessary to make a new > release containing this fix only and deploy it directly to production > later today. The problem description does NOT read like there IS ACTUAL SERVICE IMPACT at the moment; looking at the RIPE NCC service status page seems to confirm since it reports "no known problems" and no ser vice announcements either. Doing a software version change with less than a day advance notice certainly can be appropriate as an "emergency update" to deal with some service impact. How much harm is done if fix to the documentation is done a few days later while a note is posted indicating that certain errors will be fixed in the near future... ? > In this particular case we don=92t believe it is necessary to put the > release in test beforehand. The only fix is for the documentation and > this is preventing users form using the service, so it's quite urgent. > This fix should have no impact on any other part of the RIPE Database > service. I am tempted to believe your assessment; I dont have access to the changes and the resources to do my own full assessment. As I did experience 3 service impacting bugs within 12 months with UNannounced version changes I conclude that I rather see than believe. I certainly do see a need to watch more carefully how software behaves after ANY change and a non zero probability of some surprise (that could result in service impact for me). Note: knowing the schedule of upcoming changes some time in advance can be more important than actually having the ability to run tests (like due to IETF timing I could not run tests against the test server with 1.67.4 - but we did schedule preparation of critical production runs in a way that protected us against potential surprises due to the software change.) > If you have any questions then please let us know. > > Kind regards, > > Johan =C5hl=E9n > Assistant Manager Database > RIPE NCC= Best regards, Ruediger Ruediger Volk Deutsche Telekom AG -- Internet Backbone Engineering E-Mail: rv(a)NIC.DTAG.DE

5 7

New RIPE Database Release Available Soon
by Johan Åhlén 08 Aug '13

08 Aug '13

Dear colleagues, We are pleased to announce that a new release of the RIPE Database will be available soon. Details about the upcoming release, including dates, descriptions of the changes and other factors that might affect you as a user, can be found here: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.67… The first new feature is a diff functionality, which allows you to see, in detail, what changes were made between two versions of an object in the RIPE Database. Head over to RIPE Labs to read more about the diff feature: https://labs.ripe.net/Members/denis/diff-functionality-in-the-ripe-database We have also improved the way the Global Resource Service (GRS) data is imported. This allows us to present a more complete data set for all Internet resources throughout the world. This RIPE Labs article will bring you up to speed on the GRS improvements: https://labs.ripe.net/Members/denis/the-ripe-global-resource-service Lastly, we have also made several improvements to the REST API. As there are some changes, the new implementation will be deployed and running in parallel to the old version up until the next release. This provides you with time to verify your software and scripts against the new release. The implications of these changes are described in the release notes linked above. If you have any questions or comments, we look forward to hearing them! Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

2 2

[ncc-services-wg] https://www.ripe.net/ripe/policies/proposals/2013-04
by Maurice [SHQ] 06 Aug '13

06 Aug '13

https://www.ripe.net/ripe/policies/proposals/2013-04 Support +1 Met vriendelijke groet, Maurice SHQ B.V. Sterk in e-commerce hosting Klantenservice Nederland: 0165-201005 Klantenservice Belgie: 03-8081633 klantenservice(a)shq.nl / www.shq.nl Postadres: Ekelstraat 3 4726AN Heerle - NB Op al onze diensten en leveringen zijn onze algemene voorwaarden van toepassing. SHQ.nl is onderdeel van Trafego IS B.V. - KVK Breda: 58096140

1 0

2013-04 New Draft Document and Impact Analysis Published (Resource Certification for non-RIPE NCC Members)
by Emilio Madaio 25 Jul '13

25 Jul '13

Dear Colleagues The second version of the draft document for the policy proposal 2013-04 has been published. The impact analysis that was conducted for this proposal has also been published Highlight of the minor change in this version: -rewording of the second bullet point in section 2.0, as announced by the author You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2013-04 and the draft document at: https://www.ripe.net/ripe/policies/proposals/2013-04/draft We encourage you to read the draft document text and send any comments to ncc-services-wg(a)ripe.net before 8 August 2013. Regards Emilio Madaio Policy Development Officer RIPE NCC

3 2

Draft Minutes - RIPE NCC Services WG - RIPE 66
by Bijal Sanghani 19 Jul '13

19 Jul '13

Dear All, The draft minutes from the NCC Services WG at RIPE 66 are now online: https://www.ripe.net/ripe/groups/wg/services/minutes/ripe-66 Please feel free to send comments to either myself, Kurtis or the mailing list. Kind regards, Bijal Sanghani NCC Services WG Co-chair

3 2

New Procedure for RIPE Database Software Releases
by Johan Åhlén 28 Jun '13

28 Jun '13

Dear colleagues, We have recently received valuable input on how we can improve our release procedures for the RIPE Database software. In order to further reinforce our processes, we have defined a new procedure together with the Database Working Group (WG) Chairs that will address the concerns that have been raised about the stability of the Database software by the community. The purpose of the new procedure is to give you notice of what the next release will contain and how it might affect you as a user. No matter what the impact of a new feature is, an announcement will always precede the deployment to production and you will be given sufficient time to test your software. The procedure is not too far from how we have been working up until now, but will be more strictly defined and will hopefully eliminate any surprises. We propose to proceed as follows: - We will move to a four to six week release cycle for the Database software - There will be no more than three new features per release - Each new release will be announced to the WG mailing list at least two weeks before we deploy to production - In the event that we are required to deviate from what was stated in the announcement, we will announce this to the WG mailing list - The new release will be available in Test Database at least two weeks before we deploy to production - We will announce to the WG mailing list when we have successfully completed deployments to Test Database - We will announce to the WG mailing list when we have successfully completed deployments to Production Database - In the special case of required emergency fixes, we will announce this to the WG mailing list as well as the website as soon as possible - We will make a follow-up announcement to the WG mailing list and the website as soon as a fixed version has been deployed - These two emergency announcements can be combined for security reasons, or if the problem is solved in less than 30 minutes For the initial release announcements, the following template will be used: Release number Expected date of deployment to Test Database Expected date of deployment to Production Database New features Impact on existing functionality Operational improvements Impact on existing functionality Fixed bugs Impact on existing functionality Expected upcoming features for next release We hope that you will find this procedure beneficial and with your consent we would like to move ahead with it effective immediately. We also intend to publish this procedure to the website together with a roadmap of what we expect that the upcoming releases will contain. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

1 0

DB Software - release and deployment improvements
by Wilfried Woeber 28 Jun '13

28 Jun '13

Dear DB-WG, NCC-Services and Routing WG Community! Over the recent month or so, a deployment of a new version of the DB-SW, to the production environment, turned out to (potentially) have serious impact on automated router configurations in (an) operator's network(s). The issue was reported to the NCC's DB-WG Group and the specific problem has already been fixed (actually on the same day as reported). Here's the link to the service announcement page: http://www.ripe.net/lir-services/service-announcements/ripe-database-query-… However, as the incident seemes serious enough, a small group of interested people (Rüdiger, Nigel Titley, folks from the NCC and myself) started to dig a bit deeper, into what was (and is) perceived to be aspects that need review, more transparency and maybe improvement. We plan to look at some aspects, amongste others, like: - better communication regarding upcoming new SW releases - better transparency when and where (TEST DB, Production DB,...) new software will be deployed - version control and documentation But the most important thing is an improved and more transparent process to deploy new software versions *as soon as possible*! Then we can take it from there... While this message is also sent to the NCC Services and Routing WG, fyi, I'd like to suggest to have follow-up comments and discussion on the DB-WG List! Looking forward to fruitful discussions, best regards, Wilfried

1 0

[service] LIR Portal Downtime Due to Network Maintenance, Saturday 29 June
by Alex Band 27 Jun '13

27 Jun '13

Dear colleagues, On Saturday 29 June, from 07:30 UTC to 16:00 UTC, the RIPE NCC is planning network maintenance. During this maintenance, the LIR Portal and services that depend on it, such as the IP Analyser and the Resource Certification (RPKI) management interface, will be unavailable. Other RIPE NCC services are not expected to be affected. We apologise for any inconvenience this may cause. If you have any questions, please contact us at <sw-bugs(a)ripe.net>. Kind regards, Alex Band Product Manager RIPE NCC

1 0

RIPE NCC Launches New Initiatives at EuroDIG 2013
by Chris Buckridge 27 Jun '13

27 Jun '13

Dear colleagues, The RIPE NCC has posted a report on our participation at last week's EuroDIG (European Dialogue on Internet Governance) meeting in Lisbon, including two new initiatives launched by the RIPE NCC at the event: https://www.ripe.net/internet-coordination/news/about-ripe-ncc-and-ripe/rip… Best regards, Chris Buckridge External Relations Officer, RIPE NCC

1 0

RPKI Validator 2.11 with RESTful API
by Alex Band 26 Jun '13

26 Jun '13

Dear colleagues, We just released a new version of the RIPE NCC RPKI Validator with some major new functionality. The application has always been able to determine the RPKI validity state of a BGP announcement, but it was only visible in the UI. Many users have asked us to expose this functionality through an API, so it can be used for scripting and alerting. In addition, operators have expressed that they would like to know the reason of an 'Invalid' BGP announcement: whether it is an origination from unauthorised AS or if it is a more specific announcement than is allowed by the Maximum Length of the ROA. All of this is now available in version 2.11. When you supply a combination of AS and IP prefix, they will be matched against all the Validated ROA Prefixes (VRPs) that are in the cache of the RPKI Validator. The result is returned in JSON format and contains the following information: - The RPKI validity state - The VRPs that caused the state - In case of an 'Invalid' state, the reason So for example, when running this: $ curl http://localhost:8080/api/v1/validity/AS12654/93.175.147.0/24 The response will be: { "validated_route":{ "route":{ "origin_asn":"AS12654", "prefix":"93.175.147.0/24" }, "validity":{ "state":"Invalid", "reason":"as", "description":"At least one VRP Covers the Route Prefix, but no VRP ASN matches the route origin ASN", "VRPs":{ "matched":[], "unmatched_as":[{ "asn":"AS196615", "prefix":"93.175.147.0/24", "max_length":24 }], "unmatched_length":[] } } } Full documentation is available here: https://www.ripe.net/developers/rpki-validator-api You can download the application here: http://www.ripe.net/certification/tools-and-resources Kaia Global Networks offers a testbed where you can try out the functionality on a public instance of the RPKI Validator: http://195.13.63.18:8080/export We look forward to your feedback, to hear how we can improve on this functionality. Kind regards, Alex Band Product Manager RIPE NCC

1 0