December 2013 - ncc-announce - mailman.ripe.net

[news] RIPE NCC Activity Plan and Budget 2014
by Axel Pawlik 30 Dec '13

30 Dec '13

Dear colleagues, The RIPE NCC Activity Plan and Budget 2014 is now available online: https://www.ripe.net/ripe/docs/ripe-598/ The Activity Plan and Budget is the document that the RIPE NCC uses to lay out its planned activities and services for the upcoming year, as well as their associated forecast costs. The draft version of the Activity Plan and Budget 2014 was published and announced to members in September 2013 ahead of the RIPE NCC General Meeting, where members were able to discuss the document and give feedback to the Executive Board and the RIPE NCC. This final version of the Activity Plan and Budget 2014 takes into account members' feedback as well as subsequent developments in the Internet industry that affect the RIPE NCC. In order to make members aware of all updates, a new appendix has been added to the document. This appendix outlines any changes introduced to the document since it was published in September. These changes include updates to the following areas: - RIPE Registry due diligence processes - Protection against resource hijacking - The potential LISP EID Registry - Outreach efforts in Russia and Central Asia - The RIPE Academic Cooperation Initiative - Updated latest estimates (LE) regarding 2013 budget The RIPE NCC Executive Board is always happy to hear feedback on the Activity Plan and Budget. If you wish to provide feedback, you can contact the board directly at <exec-board(a)ripe.net> or you can discuss the document with fellow members at <members-discuss(a)ripe.net>. Kind regards, Axel Pawlik Managing Director RIPE NCC

1 0

[news] 91st Executive Board Meeting Summary Notes and Minutes
by Axel Pawlik 30 Dec '13

30 Dec '13

Dear colleagues, The RIPE NCC Executive Board held its 91st meeting on 12 December 2013. The Executive Board publishes the minutes of its meetings so that the RIPE NCC membership and the RIPE community will be up-to-date with the Board's thinking and ideas on all RIPE NCC-related matters. The draft minutes are available at: https://www.ripe.net/lir-services/ncc/executive-board/minutes/2013/minutes-… The following is a summary of the main items from the 91st Executive Board meeting: - The Executive Board approved the final version of the RIPE NCC Activity Plan and Budget 2014, which details the RIPE NCC's planned activities and associated costs for the upcoming year. The Executive Board encourages all members to read this document. - The Executive Board discussed the RIPE NCC reserve levels and decided to lower the fees over time and reduce the surplus - The Executive Board reviewed a RIPE NCC workflow document that outlines the approval of RIPE NCC procedures. The board approved the document and asked the RIPE NCC to publish it for the RIPE NCC membership and RIPE community. - The RIPE NCC reported that it was seeking a more suitable office location. The board supports this initiative and asked the RIPE NCC to report back when a property was identified for the board to review. - The Executive Board gave feedback on a draft job description for RIPE NCC Executive Board members. The board will work with the RIPE NCC on further defining the roles of Executive Board members. - The Executive Board approved a one-time contribution of USD 50K to ensure the continued survival of the Internet Protocol Journal. - The Executive Board approved that the RIPE NCC should execute the registry function for LISP. - The Executive Board commended the RIPE NCC for publishing the action plan resulting from the RIPE NCC Survey 2013 and asked the RIPE NCC to provide updates on progress made with the actions. You can give feedback by emailing the Executive Board directly at <exec-board at ripe.net>. RIPE NCC members can also discuss matters among the entire membership by emailing <members-discuss at ripe.net>. Kind regards Axel Pawlik Managing Director RIPE NCC

1 0

[meetings] RIPE Meeting - Call for Hosts for RIPE 71
by RIPE Meeting 23 Dec '13

23 Dec '13

Dear colleagues, Are you interested in hosting the RIPE 71 Meeting, from 9-13 November 2015? We are searching for dependable organisations to help us host the RIPE 71 Meeting outside of the Netherlands. The host helps with Internet connectivity, venue scouting, administrative and on-site support, and assists in finding local sponsors. In return, the host organisation enjoys excellent visibility among the RIPE community and the prestige of hosting a RIPE Meeting. Interested? Please find more information at: https://www.ripe.net/ripe/meetings/ripe-meetings/ripe-71/call-for-hosts You can send your proposal to: meeting(a)ripe.net. We look forward to hearing from you, The RIPE Meeting Team

1 0

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

[news] Proposed Implementation for Two-Factor Authentication
by Alex Band 11 Dec '13

11 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

1 0

[news] 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

[news] Authentication Proposal for RIPE NCC Access
by Alex Band 04 Dec '13

04 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

1 0