- ncc-announce - mailman.ripe.net

[news] 105th RIPE NCC Executive Board Meeting Summary
by Axel Pawlik 14 Apr '16

14 Apr '16

Dear colleagues, The RIPE NCC Executive Board held its 105th meeting on 31 March 2016. A summary of the meeting minutes is now available: https://www.ripe.net/publications/news/announcements/105th-ripe-ncc-executi… You can give feedback on the minutes 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

[news] RIPE NCC Members and Multiple LIR Accounts - Decisions and Next Steps
by Nigel Titley 14 Apr '16

14 Apr '16

Dear members, The RIPE NCC Executive Board would like to thank the members for their contributions to the discussion on the ability of RIPE NCC members to open additional LIR accounts. The Board initiated this discussion because it was concerned that, contrary to the spirit of the last /8 policy, there was the possibility of people acquiring IPv4 address space by opening multiple LIR accounts with the aim of transferring that address space to another entity. There were many considered and well-thought-out suggestions that represented a diverse range of opinions. Many of the suggestions put forward that could have a positive effect were matters for the Policy Development Process (PDP) to consider rather than the RIPE NCC membership. The Board believes that the matter should be taken up again at the next RIPE NCC General Meeting (GM) to be held on 25 May 2016. At the meeting, the members will be given the opportunity to hear from the Board, have a further discussion and vote on the matter. Until then, the Board resolution to temporarily suspend the ability to create additional LIRs will remain in place. The Board has decided on a measure to be taken immediately to deter the acquiring of /22s of address space with the sole purpose of transferring it to another legal entity. The RIPE NCC will therefore broaden the definition of policy transfers by including network acquisitions in the scope of the transfer policy. Therefore, all network acquisitions will fall under the RIPE transfer policy unless they are part of an organisation merger, organisation acquisition, bankruptcy or liquidation. Resources received following a policy transfer may not be transferred again to another organisation within 24 months, a limitation imposed by the RIPE community policy. This limitation does not apply to resources received through an organisation merger, acquisition, bankruptcy or liquidation. Mergers, acquisitions, bankruptcies and liquidations must be supported by official documentation issued by national authorities (e.g. Chamber of Commerce) whereas policy transfers are based on the RIPE community policies and supported by the transfer agreement signed by both parties. The RIPE NCC will update the "Transfer of Internet Number Resources and Change of a Member’s Official Legal Name" procedure and other relevant procedural documents. We will handle ongoing network acquisition requests using our current procedures for a 28-day period starting from today. All those who have requested a network acquisition will be contacted to make them aware of the situation. The Board has instructed the RIPE NCC to strengthen its due diligence procedures to clarify that transfer agreements are signed by a party that is officially authorised to do so according to national authority registration. We look forward to further discussion of the multiple LIR issue at the upcoming GM. The Board of course encourages you to continue the discussion on the members-discuss mailing list if you so wish. Registration for the upcoming GM is open and we urge all members to register so they can take part in the discussions and exercise their right to vote on this important matter. https://www.ripe.net/participate/meetings/gm/meetings/may-2016 Best regards, Nigel Titley RIPE NCC Executive Board Chairman

1 0

[GM] RIPE NCC Annual Report 2015 and Proposed Charging Scheme 2017
by Serge Radovcic 13 Apr '16

13 Apr '16

Dear members, The RIPE NCC Annual Report 2015, including the Financial Report 2015, is now available online. The Annual Report is a supporting document for the RIPE NCC General Meeting (GM), which takes place from 25-27 May 2016. The supporting documents also include the proposed Charging Scheme 2017 that members will vote on at the upcoming GM. All the documentation, including the Annual Report, is available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/supporting-d… You can find out about the GM and the elections, including how to register for voting, at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016 Annual Report Highlights ---------------------------------- The Annual Report documents the activities of the RIPE NCC in 2015 and contains the Financial Report 2015. Some other highlights in the Annual Report include: - Detailed statistics on the RIPE NCC’s allocation and assignment of Internet number resources - Statistics on IPv4, IPv6 and ASN transfers - Maps and statistics showing the various meetings and training courses held across our service region - Address hijacking in 2015 - Updates from the Chairman of the RIPE NCC Executive Board, the Managing Director of the RIPE NCC, the Executive Board Treasurer, and the RIPE NCC Senior Management Team - Much, much more… The Annual Report is only available online. It can be downloaded for those who wish to print it. We hope you take the time to read the report. If you have any feedback on it, please email <agm(a)ripe.net>. Best regards Serge Radovcic Chief Communications Officer RIPE NCC

1 0

[news] Locking unmaintained PERSON and ROLE objects in the RIPE Database
by Trudy Prins 07 Apr '16

07 Apr '16

Dear colleagues, The RIPE NCC Executive Board (EB) endorsed a proposal on how to deal with a vulnerability for RIPE Database users. Following their advice, the RIPE NCC proactively locked 848,986 unmaintained PERSON objects and 1,206 unmaintained ROLE objects on 6 April 2016. Since reaching the last /8, IPv4 address space has become more susceptible to hijacking. Unmaintained PERSON and ROLE objects are highly at risk of being found and hijacked. In addition, unmaintained PERSON and ROLE objects are an issue with regards to data protection obligations. The potential impact of abuse led us to consult with the EB on this intermediary solution before engaging with the community on the next steps. Exposing this issue without taking adequate measures would have left the RIPE NCC liable to third party damages. The proposed solution we outline below is a starting point, to be discussed by the community. Background: =========== Since 2010 it has been mandatory to protect PERSON and ROLE objects in the RIPE Database using a maintainer on "mnt-by:". A large number of PERSON and ROLE objects dating from before 2010 are still not protected in this way. Objects can be created that reference these unmaintained objects, but doing so will generate a warning. In recent years, given the scarcity of IPv4 address space, there is a higher risk of people searching for unmaintained PERSON or ROLE objects in order to pose as a resource holder to sell IPv4 space. In the case of legacy space, this could take place outside the view of the RIPE NCC if the address space is not registered with the RIPE NCC. Proposal: ========= 1) All unmaintained ROLE and PERSON objects are now locked. As the RIPE NCC will not be able to correctly check all claims on unmaintained database objects, unlocking is not available. Offering to unlock these objects could leave the RIPE NCC liable to third party damages if due diligence is not followed. 2) Furthermore, the RIPE NCC modifies the existing warning about referencing unmaintained persons/roles to a similar warning about referencing locked persons/roles. 3a) The locked objects can remain as they are. In time, all locked PERSON or ROLE objects no longer referenced by other objects could be automatically deleted: the current thinking is a 180-day deletion timeout for these locked, unreferenced objects. 3b) If there is an operational need, new PERSON or ROLE objects should be created by the object owners. This solution puts control back into the hands of the object owners. The user can follow the existing process for creating and referencing new objects. If there is a use case for supporting bulk migrations where a reference to a locked PERSON or ROLE object should be replaced, the RIPE NCC can create a wizard in the RIPE Database webupdates section of www.ripe.net <http://www.ripe.net/>. We look forward to your feedback. Kind regards, Trudy Prins Manager Software Engineering RIPE NCC

1 0

[training] Training Course: Exploring RIPE Database API
by Training Services 31 Mar '16

31 Mar '16

Dear colleagues, We are happy to announce that a RIPE NCC training course will take place on Sunday 22 May, before RIPE 72 begins on Monday 23 May, in Copenhagen. This course will focus on using RIPE Database RESTful API to programmatically manipulate RIPE Database objects. The course is free of charge and is open to anyone interested. ---------------- Course details ---------------- Exploring RIPE Database API ---------------- Course goals ---------------- By the end of this course, you will be able to perform operations on object in the RIPE Database using RESTful API. ---------------------------------------- Who will benefit from this course? ---------------------------------------- Anyone managing objects in the RIPE Database and considers automating this process or integrating with other software will find this course useful. --------------- Prerequisites: --------------- - Basic programming experience - Basic knowledge of the RIPE Database ------------------------- Course outline: ------------------------- - RIPE Database Overview - Exploring RESTful API - Using RESTful API - Building simple IPAM ---------------------------- Additional information ---------------------------- - Free of charge - Coffee and lunch will be provided - Delivered by the RIPE NCC’s Training Services ----------------------------------------- Registration for RIPE NCC members ----------------------------------------- Please register via the following page: https://lirportal.ripe.net/training/register/courseCode/LIR20160008 ------------------------------------ Registration for non-members ------------------------------------- Please fill out the following information email it to: <training(a)ripe.net>: - Email: - Course name: - Full name : - Vegetarian: yes/no Be quick - we only have 45 seats available on a first-come, first-served basis! If there is enough interest, we will continue to offer courses on different topics of interest alongside future RIPE Meetings. Kind regards, RIPE NCC Training Services

1 0

[GM] Register for the RIPE NCC General Meeting May 2016
by Axel Pawlik 30 Mar '16

30 Mar '16

Dear RIPE NCC members, On behalf of our Executive Board, I invite you to register for the RIPE NCC General Meeting (GM) May 2016. The membership will discuss important issues at the GM and there will be an election to fill two seats on the Executive Board, so I hope you will all take a few moments to register for this meeting. Find out how to register at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/registration… The GM will be held on Wednesday, 25 May from 16:00-20:00 UTC+2 at the Tivoli Hotel and Conference Center. All information on the GM is available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016?pk_campaign=… Registration - Attendance and Voting ------------------------------------- Registration for attendance and voting takes place through the LIR Portal. In order to register, you must be listed as an contact person for your organisation in the LIR Portal. You can register directly by clicking the GM Preferences link in the My LIR section in the LIR Portal: https://www.ripe.net/s/gm-registration-may-2016 Registration for electronic voting will remain open until 16:00 UTC+2 on the day of the GM, 25 May 2016. The window for casting electronic votes will remain open until Friday, 27 May at 09:00 UTC+2. If you have any questions about the registration process, please contact <agm(a)ripe.net>. Proxy Voting ------------ You can be represented by a third party who is not an authorised employee or director of your organisation. If you wish to do this, please fill out the proxy form and send it to us using the details on the form by 11 May 2016. Any proxy form sent to us after this date will not be valid. The proxy form is available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/proxy-voting… Executive Board Election ------------------------ There will be an election for two vacant seats at the GM, which are for three-year terms. The seats are to fill the places currently held by Remco van Mook and Nigel Titley, whose terms expire in May 2016. Information on how to nominate a candidate or support a nomination is available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/nominations-… All nominations and messages of support are publicly archived: https://www.ripe.net/ripe/mail/archives/agm-nominations/ If you have questions about the GM, please email us at <agm(a)ripe.net>. Best regards, Axel Pawlik Managing Director RIPE NCC Important Dates: 23 March - Call for nominations to RIPE NCC Executive Board 30 March - Open registration for GM 30 March - Open voting registration 13 April - Publish all GM documents, including RIPE NCC Annual Report and Financial Report 2015 4 May - Close nominations for Executive Board elections 11 May - Deadline for proxy vote nominations 11 May - Deadline for members to propose resolutions 11 May - Deadline to publish final GM agenda 25 May - Close registration for electronic voting 25 May - GM begins with main meeting 27 May - GM closes with votes announcement

1 0

[news] RIPE Policy Proposals - March Update
by Marco Schmidt 29 Mar '16

29 Mar '16

Dear colleagues, Here is our monthly overview of open policy proposals and their stage in the RIPE Policy Development Process (PDP). If you wish to join the discussion about a particular proposal, please do so on the relevant working group mailing list. Proposals Open for Discussion: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" Proposals Awaiting Input: 2015-05, "Revision of Last /8 Allocation Criteria" 2015-04, "RIPE Resource Transfer Policies" Proposal Overviews: PROPOSAL: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" OVERVIEW: Aims for a mandatory abuse contact for Legacy Internet Resource holders in the RIPE database. STATUS: Extended Discussion Phase WHERE TO COMMENT: Anti-Abuse Working Group: anti-abuse-wg(a)ripe.net DEADLINE: 5 April 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-01 ===== The following proposals are awaiting input before they can go any further in the PDP. PROPOSAL: 2015-04, "RIPE Resource Transfer Policies" OVERVIEW: Aims to create a single transfer policy with all relevant information on the transfer of Internet number resources, replacing text in several RIPE Policies. The proposal also introduces a 24-month holding period for IPv4 addresses and 16-bit ASNs after any change of holdership. RIPE NCC IMPACT ANALYSIS: Includes the point how the 24-month holding period for scare resources will be applied. STATUS: Review Phase – Awaiting Decision from Working Group Chair FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04 PROPOSAL: 2015-05, "Revision of Last /8 Allocation Criteria" OVERVIEW: Aims to allow LIRs to request an additional /22 IPv4 allocation from the RIPE NCC every 18 months. This would only be possible if the LIR has not transferred any IPv4 address space before. STATUS: Discussion Phase – Awaiting decision from proposer FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-05 The RIPE NCC provides an overview of current RIPE Policy Proposals on www.ripe.net: https://www.ripe.net/participate/policies/current-proposals/current-policy-… We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC

1 0

[GM] RIPE NCC Executive Board - Call for Nominations
by Axel Pawlik 23 Mar '16

23 Mar '16

Dear RIPE NCC member, The RIPE NCC is calling for nominations to the RIPE NCC Executive Board. There will be an election for two vacant seats at the RIPE NCC General Meeting (GM) on 25-27 May 2016, which are for three-year terms. The seats are to fill the places currently held by Remco van Mook and Nigel Titley, whose terms expire in May 2016. The document outlining the RIPE NCC Executive Board functions and expectations is available at: https://www.ripe.net/lir-services/ncc/executive-board/ripe-ncc-executive-bo… All those considering standing for election to the board are advised to read this information. Nominations ----------- A nomination for the appointment of a member of the Executive Board requires the support of at least five members. You must be a RIPE NCC member and a registered LIR contact to nominate a candidate or support a nomination. Nominations and support submissions should include the following information: - Your full name - Your email address - Your organisation - Your LIR RegID - Name of the candidate you wish to nominate/support - Email address of the candidate - Reason for nominating/supporting the candidate Nominations and support submissions must be submitted by Wednesday, 4 May 2016 following the guidelines outlined in article 9 of the RIPE NCC Articles of Association. To make a nomination or support a candidate, you can email the required information to <agm-nominations(a)ripe.net>. Or you can fill out the nomination form available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/agm-nominati… Excerpts from the Articles of Association are available at the end of this email. Voting -------- Voting for the appointment of the RIPE NCC Executive Board members will take place at the upcoming GM. The GM will be held on Wednesday, 27 May from 16:00-20:00 (local time UTC+2) at the Tivoli Hotel and Conference Center in Copenhagen adjacent to the RIPE 72 Meeting, which takes place from 23-27 May. The GM begins with presentation of the reports from the RIPE NCC in the RIPE NCC Services Working Group session at 16:00. The formal, members-only section of the GM starts immediately after the RIPE NCC Services Working Group session. Information on the GM is available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016?pk_campaign=… If you would like to vote but cannot attend the GM, there are two options that enable you to vote in the Executive Board elections: 1. Electronic Voting Registration to vote electronically at the GM will open on 30 March 2016. All RIPE NCC members who are registered contacts will be sent invitations by email to register to vote electronically. If you wish to vote electronically, you must register to do so by 25 May 2016 at 16:00 (local time UTC+2). Please ensure you are listed as a contact person for your organisation in the LIR Portal to ensure you receive the invitation to register. 2. Proxy Voting You can be represented by a third party who is not an authorised employee or director of your organisation. If you wish to do this, please fill out the proxy form and send it to us using the details on the form by 11 May 2016. Any proxy sent to us after this date will not be valid. If you have any questions about the GM, please email us at <agm(a)ripe.net>. Best regards, Axel Pawlik Managing Director RIPE NCC Important Dates 23 March - Call for nominations to RIPE NCC Executive Board 30 March - Open registration for GM 30 March - Open voting registration 13 April - Publish all GM documents, including RIPE NCC Annual Report and Financial Report 2015 4 May - Close nominations for Executive Board elections 11 May - Deadline for proxy vote nominations 11 May - Deadline for members to propose resolutions 11 May - Deadline to publish final GM agenda 25 May - Close registration for electronic voting 25 May - GM begins with main meeting 27 May - GM closes with votes announcement Excerpts from the Articles of Association 8.2 The Executive Board of the Association shall consist of at least three and at most seven natural persons. They shall be members of the Board in a personal capacity and do not have to be Members of the Association. Employees of the Association cannot be appointed members of the Executive Board. 9.1 The members of the Executive Board shall be appointed by the General Meeting from a list of nominees to be drawn up by the Members. A nomination for the appointment of a member of the Executive Board shall need the written support of at least five Members and shall be submitted no later than three weeks before the General Meeting. If the number of nominees exceeds the number of vacancies, the General Meeting shall elect Executive Board members in accordance with Article 18.4.

1 0

[news] IANA Stewardship Transition Moves to Final Phase
by Nick Hyrka 15 Mar '16

15 Mar '16

This message is sent on behalf of the Number Resource Organization (NRO). —————————————————————————————————— IANA STEWARDSHIP TRANSITION MOVES TO FINAL PHASE 11 March 2016, Marrakech, Morocco – An historic proposal for the global community to assume stewardship of the IANA functions, produced after nearly two years of work by the global Internet community, has been delivered to the U.S. Government for its consideration. The proposal would remove U.S. Government oversight over a set of fundamental Internet administrative functions, including management of the global pool of Internet number resources (IPv4 and IPv6 addresses and Autonomous System Numbers), and replace it with a set of arrangements for community-based oversight. The proposal, developed by the IANA Stewardship Transition Coordination Group (ICG), is based on input from three operational communities, including the Internet Number Community (those with an interest in the global management of Internet number resources). The contributions of the Internet Number Community were coordinated via a Consolidated RIR IANA Stewardship Proposal (CRISP) Team made up of community members drawn from each of the five RIR regions. CRISP Team Chair Izumi Okutani said: “The discussions that have taken place over the last two years have been a showcase for the kind of bottom-up, community-driven processes that are a central feature of the Internet Number Community. This approach has been fundamental in making the Internet a truly global resource. It is very satisfying to see the input of so many stakeholders explicitly reflected in the ICG’s proposal, and I believe that the solution presented here successfully meets the needs of the Internet Number Community, and of all IANA stakeholders.” The ICG proposal includes mechanisms for stewardship of the number-related IANA functions, as developed by the Internet Number Community. These mechanisms include a contractual Service Level Agreement signed by the RIRs (as stewards of these functions) and ICANN (as the entity responsible for management of the functions). More information on this aspect of the proposal is available here. While the ICG published the final draft of its proposal in October 2015, elements of the proposal relied upon the adoption of a set of recommendations regarding the accountability of ICANN to its community. These recommendations were developed separately by a Cross Community Working Group on Enhancing ICANN Accountability (CCWG) and were adopted by the ICANN Board at its meeting this week in Marrakech, Morocco. The Board was at that point able to pass on both the ICG and CCWG documents to the National Telecommunication and Information Administration (NTIA), an agency of the U.S. Government. “The events of this week, here at ICANN 55 in Marrakech, represent another significant step in the long process to better operationalize the global community’s shared stewardship of the IANA functions,” said Number Resource Organization Chair and LACNIC CEO Oscar Robles. “We have not reached the end of this process yet, and we respect the attention that the U.S. Government must give to this proposal before making what will be a historic decision. At this point though, we recognize the achievement that this proposal represents: a huge, global community of people from different sectors and stakeholder groups has achieved agreement on a complex plan to achieve something of huge importance. It is something about which we, as a community, should feel justifiably proud, and it is a testament to the effectiveness of the multistakeholder model. The Regional Internet Registries have publicly supported the progressive steps taken by the U.S. Government over the years to reduce its oversight of global Internet administrative functions. Since the NTIA’s announcement in 2014, we have been pleased to help facilitate our communities’ contributions to this important IANA stewardship transition process. We now stand ready to work with ICANN and all of the IANA stakeholders towards full implementation of the ICG and CCWG proposals.” The U.S. Government will now review the proposal to ensure that it meets the criteria set out by the NTIA when they first announced their intention, in March 2014, to pass stewardship of the IANA functions to the global community. If approved, the RIRs and ICANN will continue their work towards implementation of the proposal, which will be completed prior to the expiration of ICANN’s current contract with NTIA in September 2016.

1 0

[news] Simplifying RIPE Registry Updates: Milestone 2
by Alex Band 10 Mar '16

10 Mar '16

Dear colleagues, We have just completed milestone two in our project to make updating the RIPE Registry easier and more efficient for LIRs. In this release, you will now be able to easily select resources you wish to transfer to another party. The wizard will take policy restrictions and exceptions such as Legacy resources into account, ensuring you only submit a request for eligible resources. We encourage everyone to submit feedback on the usability of the new wizard. It is aimed at making the process easier, more structured and less error prone, but that also means some options will be more limited. For example, only the offering party can request a transfer using this workflow. We would like to give you four weeks to submit your feedback. During this time, you can still submit your request using email if the wizard forms a roadblock. We will make small tweaks and improvements to the wizard if needed, after which it will become the only method to submit transfer requests. You can read about this project in more detail on RIPE Labs: https://labs.ripe.net/Members/matt_parker/keeping-the-registry-up-to-date You can find the new request form here: https://my.ripe.net/#/update-registry We will keep you updated as we complete further milestones. If you have any feedback, please don’t hesitate to reply to this email. Kind regards Alex Band Product Manager RIPE NCC

1 0