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

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

2013-04 New Policy Proposal (Resource Certification for non-RIPE NCC Members)
by Emilio Madaio 17 Jun '13

17 Jun '13

Dear Colleagues, A new RIPE Policy Proposal has been made and is now available for discussion. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2013-04 We encourage you to review this proposal and send your comments to <ncc-services-wg(a)ripe.net> before 5 June 2013. Regards Emilio Madaio Policy Development Officer RIPE NCC

17 42

Resource Certification for non-RIPE NCC Members
by Erik Bais 16 Jun '13

16 Jun '13

Dear community members of the AP WG and the NCC Services WG, As you may have seen, Ive created a policy proposal to ask the RIPE NCC to allow Resource Certification for non-RIPE NCC member resource holders. (IXP / Legacy space and PI space holders) Currently we are in the phase: Discussion Open for discussion And I would like to invite you to the service wg mail list for your support for this policy and a discussion on wording of the policy. For those that are not subscribed to the NCC Services mail-list -=> http://www.ripe.net/mailman/listinfo/ncc-services-wg/ During the creation of the policy I made a small error in the intention to limit the policy to entities in the RIPE NCC service region and the policy currently states: The Internet resources reside within the RIPE NCC service region Ill update this in the review phase. Im not sure yet if we need to skip that part entirely or change it to the actual intention. Your input and stated support on the NCC Services WG mail list would be highly appreciated. Kind regards, Erik Bais Link to the policy proposal: https://www.ripe.net/ripe/policies/proposals/2013-04

13 16

2012-08 Review Period extended until 1 July 2013 (Publication of Sponsoring LIR for Independent Number Resources)
by Emilio Madaio 16 Jun '13

16 Jun '13

Dear Colleagues, The Review Period for the proposal 2012-08, "Publication of Sponsoring LIR for Independent Number Resources", has been extended until 1 July 2013. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-08 We encourage you to review this policy proposal and send your comments to <ncc-services-wg(a)ripe.net>. Regards, Emilio Madaio Policy Development Officer RIPE NCC

2 1

2013-04 to Review phase
by Lindqvist Kurt Erik 13 Jun '13

13 Jun '13

All, The WG chairs have decided to proceed with moving the 2013-04 proposal to the review phase. Our reasoning for this is 1/ There seems to be broad support for the proposal 2/ The changes flagged by the author for the new version are minimal 3/ We believe that having the RIPE NCC impact analysis available for the proposal will help in the discussions I would like to stress that this step forward in the PDP does not make this proposal more or less likely to become a final policy, but rather it will give us a more complete document to have a discussion around. Last, as for the issue raised by Peter, if members DO believe that acceptance of 2013-04 as a policy in a possible future last-call is dependent on symmetry with PA/other status I would like to bring this to the list. Kurtis & Bijal

1 0

2012-07 New Draft Document and Impact Analysis Published (RIPE NCC Services to Legacy Internet Resource Holders)
by Emilio Madaio 12 Jun '13

12 Jun '13

Dear Colleagues, The draft document for the version 3.0 of the proposal described in 2012-07, "RIPE NCC Services to Legacy Internet Resource Holders", has been published. The impact analysis that was conducted for this proposal has also been published. Highlight of the main differences from version 2.0 -rewording of the first paragraph of the Introduction into two new paragraphs -new definition of Legacy Internet Resources -added definition of Registry Service Element -additional text in the Scope section -rewording and new text in sections 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 5.0 -removed the reference section 6.0 You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2012-07 and the draft document at: https://www.ripe.net/ripe/policies/proposals/2012-07/draft We encourage you to read the draft document text and send any comments to before 3 June 2013. Regards Emilio Madaio Policy Development Officer RIPE NCC

11 19