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

New RIPE NCC PGP Key
by Ingrid Wijte 17 Dec '13

17 Dec '13

[Apologies for duplicate e-mails] Dear Colleagues, On Monday, 6 January 2014 we will start using our 2014 key to sign e-mails from our ticketing system. The new key has been signed by the old key as described in the key-management policy on our web site: https://www.ripe.net/lir-services/resource-management/contact/pgp-authentic… The old key remains valid until Wednesday, 29 January 2014. If you have any questions about this, please contact <ops(a)ripe.net>. Kind Regards, Ingrid Wijte RIPE NCC

1 0

Proposed Implementation for Two-Factor Authentication
by Alex Band 12 Dec '13

12 Dec '13

Dear colleagues, Firstly, I would like to thank all who provided feedback on our authentication proposal for RIPE NCC Access. Many responded to the request for feedback, both publicly and privately, which is very encouraging to see. Based on your input, and the fact that this functionality is very rarely used, we would like to propose the following: 1. Discontinue X.509 identity certificate login from 1 February 2014 - All users who currently have a certificate will be contacted individually - Users will only use their RIPE NCC Access username and password to log in from 1 February 2014 - Note: a lost password can be recovered at https://access.ripe.net/forgot-password 2. Build an implementation for two-factor authentication for RIPE NCC Access, supporting at least: - HMAC-Based One-Time Password (HOTP) - Time-Based One-Time Password (TOTP) We would like to plan the development effort and scheduling before the end of the year and inform you about our roadmap once the project plan is in place. Please let us know if you have any comments or questions. Kind regards, Alex Band Product Manager RIPE NCC

2 1

IPv6 support in the IP Analyser API
by Alex Band 11 Dec '13

11 Dec '13

Dear colleagues, We are incrementally adding support for IPv6 in the IP Analyser toolset. The first piece of functionality that we deployed is the API. You can read more about this feature at: https://www.ripe.net/data-tools/developer-documentation/the-lir-portal-ip-a… Please do not hesitate to contact us if you have any feedback or questions. Kind regards, Alex Band Product Manager RIPE NCC

1 0

Authentication Proposal for RIPE NCC Access
by Alex Band 06 Dec '13

06 Dec '13

Dear colleagues, In our RIPE NCC Access authentication system, we offer the ability to log in using an X.509 identity certificate instead of a username and password. This functionality was transferred from the legacy authentication system we used to have, without evaluating the value of this feature at the time. Since then, we have encountered several implementation, user interface and support issues surrounding this feature, while it is used by less than 0.7% of the users with a RIPE NCC Access account. Most importantly, the functionality does not actually offer any additional security. This is something that is provided by true two-factor authentication. We would like to propose to put this functionality in maintenance mode, meaning that it would be provided as it is without a service guarantee. Alternatively, it could be removed altogether. This would free us of a maintenance and support burden, meaning that we can spend these resources on other valuable services. If the membership approves, the RIPE NCC could investigate ways to implement true two-factor authentication for RIPE NCC Access. We look forward to hearing your feedback. Kind regards, Alex Band Product Manager RIPE NCC

16 17

Follow up on implementation of Resource Certification (RPKI) for PI End User Resources
by Alex Band 26 Nov '13

26 Nov '13

Dear colleagues, Over the last few weeks, we have been consulting the RIPE community on the practical implementation of providing Resource Certification (RPKI) for Provider Independent (PI) End Users. In about two weeks, we plan to start with the implementation and, based on the feedback that you have provided, we would like to offer the following two solutions: 1. A management interface for sponsoring LIRs in the LIR Portal Sponsoring LIRs will be able to issue access credentials for the RPKI Management interface to either themselves if they manage ROAs on behalf of the PI End User, or directly to the PI End User if they have requested to set up and maintain ROAs. 2. A form on the RIPE NCC website, allowing PI End Users to request access directly from the RIPE NCC PI End Users will be able to log in with their RIPE NCC Access account, enter the resources they would like a certificate for and authenticate against the INETNUM database object to prove they have authoritative control over the address space. If you have any feedback, please do not hesitate to respond to this message. Kind regards, Alex Band Product Manager RIPE NCC P.S. The RIPE NCC has explained the implementation options and associated cost at the following locations: http://www.ripe.net/ripe/mail/archives/ncc-services-wg/2013-March/002145.ht… http://www.ripe.net/ripe/mail/archives/ncc-services-wg/2013-March/002149.ht… http://www.ripe.net/ripe/mail/archives/ncc-services-wg/2013-March/002252.ht… http://www.ripe.net/ripe/mail/archives/ncc-services-wg/2013-March/002256.ht… http://www.ripe.net/ripe/mail/archives/ncc-services-wg/2013-October/002587.…

2 1

RPKI Validator 2.13 released
by Alex Band 25 Nov '13

25 Nov '13

Hello everyone, We just released RPKI Validator 2.13 and I would just like to highlight a couple of important improvements and fixes. 1. Single, unified configuration file We recently received a request to allow overriding the default paths of the application to allow Debian packaging. This meant we ended up with so many startup flags and environment variables that we decided to put every user configurable option together in one single file. You can choose your own name and path for the config file, to allow for easy updating without overwriting your preferences. 2. Application health and trust anchor monitoring Quite some users have asked us to implement monitoring, so they can keep an eye on whether the application itself is running properly and if the RPKI repositories are available and serving data. Application health monitoring currently only checks if the rsync binary can be found and executed. For Trust Anchor monitoring we built a dedicated page. For example: http://localcert.ripe.net:8088/trust-anchor-monitor/44a4f26e67 Both are a basic, initial implementations. We’re actively looking for feedback on which checks you would like to see and how you would like to be able to implement them in your monitoring setups. 3. Deep linking You can specify an AS Number or prefix in the URL of the ROA and BGP Preview pages to get direct, bookmark-able access to information. For example: - http://localcert.ripe.net:8088/roas?q=2001:7fb:fe01::/48 - http://localcert.ripe.net:8088/bgp-preview?q=AS12654 4. Bug and conformance fixes At IETF88 in Vancouver we did some rigorous testing with other implementors to see how the application handles malformed objects. A couple of bugs and other anomalies came to light that have been fixed in this version. You can download RPKI Validator 2.13 here: https://www.ripe.net/lir-services/resource-management/certification/tools-a… We recommend that you update to this release. As always, we look forward to your feedback. Kind regards, Alex Band Product Manager RIPE NCC

1 0

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

19 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 - RIPE 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

2012-07 Last Call for Comments (RIPE NCC Services to Legacy Internet Resource Holders)
by Marco Schmidt 18 Nov '13

18 Nov '13

Dear colleagues, The proposal described in 2012-07, RIPE NCC Services to Legacy Internet Resource Holders, is now in its Concluding Phase. The RIPE NCC Services Working Group co-Chairs have declared that consensus for the proposal has been reached and it will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of these coming four weeks of Last Call is to give the community the opportunity to present well-justified objections in case anyone missed the previous two phases and want to oppose the proposal. Any objection must be made by 17 December 2013 and must be supported by an explanation. If no substantive objections are raised by the end of Last Call, the proposal will complete the PDP and will be evaluated by the co-Chairs of all RIPE Working Groups for consensus. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-07 Please e-mail any final comments about this proposal to ncc-services-wg(a)ripe.net before 17 December 2013. Regards Marco Schmidt Policy Development Office RIPE NCC

1 0

2012-07 RIPE NCC Services to Legacy Internet Resource Holders - moving to last call
by Bijal Sanghani 18 Nov '13

18 Nov '13

Greetings colleagues, The NCC Services working group co-chairs have concluded that policy proposal 2012-07 - RIPE NCC Services to Legacy Internet Resource Holders will now move to last call, we believe consensus has been reached. During the last call phase the community still has an opportunity to present any sound objections that may have been missed in the previous two phases. Marco will send a mail shortly with full details of the last call shortly. Best regards, Kurtis and Bijal NCC Services WG co-chairs

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