- ncc-announce - mailman.ripe.net

[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

[news] RIPE NCC Receives /15 from IANA's Recovered Pool
by Andrea Cima 02 Mar '16

02 Mar '16

Dear colleagues, Yesterday, on 1 March 2016, the RIPE NCC and other Regional Internet Registries (RIRs) were each allocated the equivalent of a /15 of IPv4 address space from the Internet Assigned Numbers Authority (IANA). The RIPE NCC received the IPv4 address ranges 45.65.64.0/18, 147.78.0.0/16, 192.144.0.0/18 and 192.145.0.0/17. We are currently adding these to our available pool. Following the exhaustion of IANA's free pool of IPv4 addresses in 2011, when the RIRs received their final /8s, a global policy caused IANA to create a recovered pool of leftover and returned IPv4 address blocks. This policy was ratified by all five RIR communities in 2012 and stated that IANA would begin making equal, periodic allocations from the recovered pool when the first RIR reached a /9 of remaining addresses. This point was reached by LACNIC, the RIR for Latin America and the Caribbean on 20 May 2014, triggering the global policy and the first post-exhaustion allocation from IANA. You can read the global policy here: https://www.icann.org/resources/pages/allocation-ipv4-post-exhaustion-2012-… With the current policy in place, the RIPE NCC will receive one-fifth of any recovered addresses in the pool every six months (every March and September). The RIPE NCC will continue to distribute these according to the current last /8 policy, under which Local Internet Registries (LIRs) may receive a one-time /22 allocation (1,024 addresses). It is important that network operators continue to deploy IPv6 on their networks to ensure the future growth of the Internet. The RIPE NCC's IPv6 Act Now website provides more information about IPv6 deployment: https://www.ripe.net/publications/ipv6-info-centre Andrea Cima Registration Services Manager RIPE NCC

1 0

[meetings] ENOG 11 Registration Now Open
by ENOG 23 Feb '16

23 Feb '16

Dear colleagues, Registration is now open for the ENOG 11/RIPE NCC Regional Meeting in Moscow, 7-8 June 2016. The meeting is free of charge and open to everyone. Register here: http://www.enog.org/meetings/enog-11/registration The ENOG Meeting is an ideal place for network operators in Russia, as well as from other countries of Commonwealth of Independent States and Eastern Europe, to discuss challenges, tools, experiences and best practices in the following areas: Internet development trends - New technologies and applications - Evolution of the Internet ecosystem - Analytics and prediction of Internet development Internet coordination, governance and regulatory practices - Internet-related legislation and its impact, multi-stakeholder model, challenges and opportunities - Public initiatives and projects in the areas of Internet governance and coordination, research and deployment of new technologies Peering and Internet exchange points: - Business, technical and social aspects of peering and interconnection Network operations and security - Operational experience and best current practices, security trends and technologies Key Internet technologies - Real-life IPv6 and DNSSEC deployment experience, trends and statistics Content delivery - Technology, architecture and business models Call for Presentations ---------------------- The ENOG Programme Committee (PC) is now seeking content proposals from the community for the plenary session presentations, panels, workshops and lightning talks. More information is available at: http://www.enog.org/meetings/enog-11/cfp RACI ---- The RIPE Academic Cooperation Initiative (RACI) will cover the meeting ticket, travel and accommodation of academics to present their research at ENOG 11. The deadline to apply is 12 April. Read about the initiative here: https://www.ripe.net/raci ENOG 11 on Twitter and Facebook ------------------------------- Follow #ENOG11 Join the Facebook ENOG Meetings page: https://www.facebook.com/ENOG.org See you in Moscow! Martina de Mas Conference Coordinator RIPE NCC (On behalf of the ENOG Organising Committee)

1 0

[service] Mailing List Technical Issues
by Serge Radovcic 17 Feb '16

17 Feb '16

Dear colleagues, We recently discovered an issue affecting subscriptions to the <ncc-announce(a)ripe.net> mailing list. An error introduced into our automated processes was preventing subscription changes made via the LIR Portal from being reflected on this mailing list. This issue was in effect from 1 September 2015 and has now been resolved. The majority of you will not have been affected by this issue. However, during this time members were prevented from being subscribed and unsubscribed to the mailing list, and any changes that members may have made to their contact email used to receive messages from this list were not processed. These issues have now been resolved and no action is required on your part. A record of all emails sent to <ncc-announce(a)ripe.net> is available in the archives: https://www.ripe.net/ripe/mail/archives/ncc-announce/ All members specifically affected by this issue will receive a separate email. The <members-discuss(a)ripe.net> mailing list was also affected and subscribers to that list have also been notified. No other mailing lists were affected. Timely communications with our members is very important to us, and we sincerely regret this error. We have introduced measures to ensure this doesn’t happen again, and we apologise for any inconvenience this may have caused. Kind regards, Serge Radovcic Chief Communications Officer RIPE NCC

1 0

[news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
by Nigel Titley 11 Feb '16

11 Feb '16

Dear colleagues, The RIPE NCC Executive Board would like to ask the membership to discuss the issue of RIPE NCC members opening additional LIR accounts. There were comments at the RIPE NCC General Meeting (GM) in November 2015 that members having the ability to open additional LIR accounts, each of which can request a /22 of IPv4 address space, may run against the spirit of the last /8 policy. In light of this, the Board decided to temporarily suspend the ability of RIPE NCC members to open additional LIR accounts. The RIPE NCC began to allocate IPv4 address space from the last /8 policy on 14 September 2012. Since that time the RIPE NCC has allocated more than 8,600 /22s, yet there remains 0.94 of a /8 still in the pool. ACTION REQUIRED: The Board asks the membership to provide their opinion on and discuss the following points: 1. Is the activity of members opening additional LIR accounts a problem that must be prevented? 2. If this activity is a problem that must be prevented, what action should the RIPE NCC take to attempt its prevention? Statistics pertinent to this discussion are available in this article on RIPE Labs: https://labs.ripe.net/Members/laura_cobley/ripe-ncc-members-and-multiple-li… The Board asks that members discuss this issue on the Members Discuss mailing list <members-discuss(a)ripe.net>. The Board will monitor the discussion and will review it at the next Executive Board Meeting on 31 March 2016. Depending on the outcome of that meeting, the Board may propose a resolution for members to vote on at the RIPE NCC General Meeting in May 2016. Best regards, Nigel Titley RIPE NCC Executive Board

1 0

[news] RIPE NCC to start publishing opaque organisation ID in RIR stats
by Tim Bruijnzeels 04 Feb '16

04 Feb '16

Dear colleagues, The format for the RIR Statistics file has been modified by the RIRs: opaque organisation IDs are added to the statistics. The RIPE NCC is now also modifying its statistics to be in line with this change. In order to avoid issues for scripts, the RIPE NCC is rolling out the modification in a phased approach: 9 December 2015: Introduce new format 3 February 2016: New format takes precedence 2 March 2016: Old format deleted The details of the new format and each of the above phases are documented here: ftp://ftp.ripe.net/ripe/stats/RIR-Statistics-Exchange-Format.txt Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC

1 1

[news] RIPE Policy Proposals - February Update
by Marco Schmidt 04 Feb '16

04 Feb '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: NEW: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" 2015-04, "RIPE Resource Transfer Policies" Proposals Awaiting Input: 2015-05, "Revision of Last /8 Allocation Criteria" ===== Proposal Overviews: NEW 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: Discussion Phase WHERE TO COMMENT: Anti-Abuse Working Group: anti-abuse-wg(a)ripe.net DEADLINE: 26 February 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-01 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: Details how the 24-month holding period for IPv4 addresses and 16-bit ASNs will be applied. STATUS: Review Phase WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 3 March 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04 ===== The following proposals are awaiting input before they can go any further in the PDP. 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

[service] The "changed:" attribute will be deprecated from the RIPE Database release on Monday, 1 February 2016
by Tim Bruijnzeels 02 Feb '16

02 Feb '16

Dear colleagues, As requested by the RIPE Database Working Group, the RIPE NCC has been working on deprecating the “changed:” attribute in the RIPE Database. This attribute was used mostly to determine when database objects were last changed, but in practice the attribute was poorly maintained. We are now in the process of replacing the “changed:” attribute by the server-generated attributes “created:” and “last-modified”. We are conducting the replacement in three phases*: 1. (Completed) 28 April 2015 “created:” and “last-modified:” were introduced to all objects 2. (Completed) 13 July 2015 “changed:” became optional for all objects 3. 1 February 2016 “changed:” will be deprecated from all objects When phase 3 is deployed to production we will remove the “changed:” attribute from all objects in the RIPE Database. However, contrary to the earlier plan communicated on this, we will not reject object updates if they include the “changed:” attribute. Instead, we will remove the “changed:” attribute from the object and issue a warning, but accept the remaining object (provided it passed other validation rules). The reason for this is that we still see a large number of updates that include the “changed:” attribute. We expect this number to go down over time when the “changed:” attribute is removed from the object templates, and when the attribute is no longer present on objects that are being updated. We will monitor this carefully over the coming months before implementing stricter regulations concerning the attribute. However, users are still strongly advised to exclude the "changed:" attribute in updates, but rather to rely on "created:" and "last-modified:", or use "remarks:" instead. Phase 3 was deployed to the RIPE Database Release Candidate environment on 22 December, and an announcement was sent to the RIPE Database Working Group along with a request to test the changes and report issues to the RIPE NCC. No issues have been reported so far. If no issues are found over the coming two weeks, it is our intention to deploy this release to production on Monday, 1 February. With this email we also want to make sure that those who are not following the RIPE Database Working Group discussions are aware of this pending change and have an opportunity to run their own tests. Please let us know if you have any comments or concerns, Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC *: https://labs.ripe.net/Members/tim/deprecating-the-changed-attribute-in-the-…

1 1