- ncc-announce - mailman.ripe.net

[news] Proposed Implementation of Resource Certification for non-RIPE NCC Members
by Alex Band 16 Jan '14

16 Jan '14

Dear colleagues, We have been working on the implementation of 2013-04, "Resource Certification for non-RIPE NCC Members", and would like to give you an overview of our proposed plan for certifying address space held by Provider Independent (PI) End Users. You can find the full details below. In summary: 1. We propose to only issue certificates for PI End User resources if an End User Assignment Agreement has been submitted and verified by the RIPE NCC and all internal RIPE Registry records match with the associated information in the RIPE Database 2. Users will no longer be able to update the "org-name:” attribute in the organisation object without RIPE NCC involvement. This attribute will only be locked if the organisation object is referenced from a resource object. With this step we are enforcing an existing business rule. 3. RIPE NCC Access authorisation will be added to the RIPE Database. This will simply be an additional value for the "auth:" attribute, referencing your RIPE NCC Access account. Detailed explanation: Currently, when a PI resource is assigned to an End User, we make a record of the organisation name and the organisation-id in our registry. This information is reflected in the related inetnum object for the resource (the org-id attribute), as well as the organisation object (the org-name attribute). However, it is possible that these informational elements can fall out of sync, as the End User is free to update these objects without involving the RIPE NCC. This can negatively impact the accuracy of the registry. One of the primary goals of issuing resource certificates is to make the RIPE Registry as accurate and robust as possible. Therefore, we propose to only issue certificates for PI End User resources: 1. If an End User Assignment Agreement has been submitted and verified by the RIPE NCC 2. If all internal RIPE Registry records match with the associated information in the RIPE Database During the request procedure, we would perform checks to see if the resources are eligible for certification. If all of the records in the RIPE Registry and RIPE Database match, the PI End User or Sponsoring LIR would be able to request a certificate without interaction with the RIPE NCC. However, if registry and database information are out of sync, we would ask you to first resolve this (with our help) to ensure that all records match correctly. In this implementation, you will no longer be able to update the "org-name:” attribute in the organisation object without RIPE NCC involvement. This attribute will only be locked if the organisation object is referenced from a resource object. This would ensure that our registry records remain accurate at all times. Additionally, the RIPE NCC plans to launch a project where we will proactively match the RIPE Registry and RIPE Database records in cooperation with the resource holder. Another aspect we need to implement is the association of a RIPE NCC Access account with the person who has authoritative control over the resources. In order to achieve this, we will introduce the ability to add a RIPE NCC Access account to a MNTNER object in the RIPE Database. Practically, this will simply be an additional value for the "auth:" attribute, referencing your RIPE NCC Access account. This will immediately fulfil a long-standing user request to be able to update RIPE Database objects with your RIPE NCC Access account, making authentication between different RIPE NCC services more seamless. Please do not hesitate to contact us if you have any questions. Kind regards Alex Band Product Manager RIPE NCC

1 0

[service] Report on Wednesday's Outage
by Brian Riddle 10 Jan '14

10 Jan '14

Dear colleagues, We are currently upgrading our network. On Wednesday, between 15:42 and 17:27 (UTC+1), while performing a clean-up operation on our network equipment, we experienced an outage on our network which affected our virtual environment. This caused a number of our services to be unavailable for a period of time, ranging from 20 minutes to 1 hour and 45 minutes. Major services affected: 15:42 - 16:02 Internal network 15:42 - 16:08 RIPE Database 15:42 - 16:50 LIR Portal 15:42 - 16:55 www.ripe.net 15:42 - 17:27 RIPE Labs Major services not affected: DNS, K-root. As a result, we are reviewing our network maintenance procedures to minimise the risks of this occurring again. We apologise for any inconvenience that this may have caused. Kind regards Brian Riddle IT Manager RIPE NCC

1 0

[service] Technical Outage Resolved
by Nick Hyrka 08 Jan '14

08 Jan '14

Dear colleagues, At 15:45 Amsterdam time, the RIPE NCC experienced a technical outage affecting a number of our services. >From 16:15, we were able to recover some services and by 17:45 all were fully functional. We apologise for any inconvenience this may have caused. Regards, Nick Hyrka Communications Manager RIPE NCC

1 0

[service] RIPE NCC Technical Outage
by Nick Hyrka 08 Jan '14

08 Jan '14

Dear colleagues, We are currently experiencing a technical outage. Our engineers are currently trying to resolve the issue. We will provide updates as the situation changes. Regards, Nick Hyrka Communications Manager RIPE NCC

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

[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