- ripe-list - mailman.ripe.net

New Deadline for RIPE Chair Nominations
by Daniel Karrenberg 16 Dec '19

16 Dec '19

Good morning, at the end of the previous RIPE Meeting I made a call for you to nominate persons for RIPE Chair and Vice Chair. The deadline was yesterday and we have received a total of 2 (two) nominations, one for chair and one for vice chair. While this would make the task of the committee an easy one ;-), it has also been brought to my attention that the call was not very widely known. Many people seem to have missed it in all the excitement of the Rotterdam meeting. Even the current RIPE chair, Hans Petter, missed it. While working on the time-line for the NomCom I also realised that there is no reason to set such a short deadline. ripe-728 does not prescribe this either. ripe-728 also calls for pragmatism in a situation like this. Therefore I now set a new deadline: March 29th 23:59 UTC. This will also allow for the NomCom itself to canvass for Nominations. In the meantime I will work to give this call some more publicity. Daniel Karrenberg Chair of the 2019-2020 RIPE NomCom Forwarded message: > From: Daniel Karrenberg <chair(a)ripe-nomcom.org> > To: RIPE List <ripe-list(a)ripe.net> > Subject: Who will be the next RIPE Chair .... and Vice Chair ? > Date: Thu, 17 Oct 2019 12:01:51 +0200 > > Dear RIPE participants, > > Next year, a nominations committee (NomCom) will select two people to > fill the positions of RIPE Chair and Vice Chair, with help from the > wider community. As chair of the 2019-2020 RIPE NomCom, I invite you > to nominate candidates for these positions. > > As members of the RIPE community, you will have some idea of what the > RIPE Chair is responsible for and what kind of person you would like > to see in this role - and the revived Vice Chair role. Please think > about suitable candidates, talk with them, discuss this with your > peers, and nominate people who will have the support of the community. > > You may nominate any member of the RIPE community for either position. > Self-nominations are also permitted. NomCom members are not eligible > to be considered. > > You might also consider volunteering for the NomCom. I have made a > separate call for this, which you can find on the ripe mailing list. > > Send your nominations to <nominations(a)ripe-nomcom.org> and include a > description of the skills or expertise that make your candidate a > desirable choice. Please also include a working email address or > telephone number for the nominee and indicate whether they are aware > of your nomination. > > The Nomcom will also be interested in your opinion about the > performance of the incumbent, Hans Petter Holen. > > The deadline for all nominations is Sunday, 15 December 2019. > > You can find more information in the relevant RIPE Documents: > > ripe-714: A brief description of the RIPE Chair’s role. > ripe-727: Information about the selection process. > ripe-728: Detailed information about the NomCom > > I am happy to answer any further questions you may have. > > Daniel Karrenberg > Chair of the 2019-2020 RIPE NomCom

1 0

ASO Announces Support for Fundamental Bylaws Amendment to Article 18 of the ICANN Bylaws
by Antony Gollan 03 Dec '19

03 Dec '19

This message is sent on behalf of the Number Resource Organization (NRO). ASO Announces Support for Fundamental Bylaws Amendment to Article 18 of the ICANN Bylaws In its capacity as a Decisional Participant in the Empowered Community, the NRO EC (acting as the ASO) has agreed to support the Fundamental Bylaws Amendment to Article 18, Section 18.7(b) of the ICANN Bylaws relating to the composition of the IANA Naming Functions Review as posted by the ICANN Board according to its Resolution 2019.09.08.05. The ICANN Empowered Community Administration was informed of the ASO’s decision on Wednesday 27 November 2019. Process In accordance with its role as a Decisional Participant in the Empowered Community, the NRO reviewed the proposed change and concluded that this ICANN Bylaws change would not impact the Internet Number community and allows ICANN to remain accountable to its Bylaws-mandated mechanisms. As per Article 3 of the ASO Procedures for ICANN Empowered Community Powers, the RIR communities were informed and asked for feedback. No feedback was received. As per Article 5 of the procedures, the NRO EC subsequently held a teleconference on 26 November, during which the NRO EC determined whether to support, reject or abstain from approving the Bylaw Change. Further Information: – Announcement: ASO Use of Empowered Community Powers for ICANN Fundamental Bylaw Change: https://www.nro.net/aso-use-of-empowered-community-powers-for-icann-fundame… Regards Antony Gollan Senior Communications Officer RIPE NCC

1 0

rob
by Randy Bush 02 Dec '19

02 Dec '19

four years ago today, the long-time chair and steady calm hand of the ripe community died. rob, we miss you. randy

2 1

RIPE NCC Managing Director Recruitment
by Christian Kaufmann 29 Nov '19

29 Nov '19

Dear fellow RIPE and Internet community members, As previously announced, the Executive Board is hiring a new Managing Director for the RIPE NCC via a specialised executive search company. Hagoort & Partners / IRC Netherlands is supporting the RIPE NCC in the search and selection of candidates, and the recruitment process. Patrick Westerburger is the contact person for this. A description of the Managing Director job profile and requirements is available at: https://www.ripe.net/about-us/staff/careers-at-the-ripe-ncc/vacancy/148244 If you are interested in this position, you can address your application and motivation letter, in English, to <Pwesterburger(a)hagoort.com> before 1 January, 2020. Kind regards, Christian Kaufmann Chairman of the RIPE NCC Executive Board

1 0

RIPE NCC Academy unavailable from 2-27 January 2020
by RIPE NCC Academy 28 Nov '19

28 Nov '19

Dear colleagues, The RIPE NCC Academy will not be available from 2-27 January 2020 as we are upgrading the platform and changing how we offer digital badges and certificates. Here’s what we’re changing: ------------------------------------------ *Important Information* ------------------------------------------ If you are currently following a course, or have earned a badge or certificate from the RIPE NCC Academy: - Going forward, we will no longer issue certificates through the RIPE NCC Academy. - Badges earned by completing activities in the Academy courses will also be removed. - If you would like to receive a RIPE NCC Academy certificate, make sure to finish any incomplete courses before 2 January 2020. Your progress in a course will not be saved beyond this date. - Please download and save your RIPE NCC Academy certificates as they will not be available from 2 January onwards. - The new RIPE Database course will be available after 27 January 2020. - We will issue verifiable digital badges and certificates through the RIPE NCC Certified Professionals programme from 2020 onwards. ------------------------------------------ A fresh RIPE Database Course ------------------------------------------ The RIPE Database online course will return with new, up-to-date content. This content is aligned with the RIPE NCC Certified Professionals exam. Other major changes include making the modules shorter, meaning that you can learn about a topic in 10-20 minute sessions. We have also improved the interactivity and have added exercises to help you practice your RIPE Database skills. ------------------------------------------ Training Database Upgrade ------------------------------------------ The Training Database is a copy of the RIPE Database for learners. It will be updated to the latest version of the RIPE Database software and, from now onwards, it will be synced with every future update of the RIPE Database software. While the bad news is that we will take the Academy offline for most of January 2020, the good news is that it will come back with improved functionality and a better learning experience. You can read more about these changes on RIPE Labs: https://labs.ripe.net/Members/ulka_athale_1/revamping-the-ripe-ncc-academy If you have any questions, write to us at <academy(a)ripe.net> Best regards, Sandra Brás E-Learning Programme Manager RIPE NCC

1 0

Germany Country Report Published as IGF Begins
by Suzanne Taylor 26 Nov '19

26 Nov '19

Dear colleagues, What is the longest path a packet might take between two users in Berlin? Which countries have received the most IPv4 transfers from Germany? How many paths are available to traffic entering Germany from the rest of the world? These are some of the questions we asked when we put together our latest country report, this time looking at Germany: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-ncc-country-report… The report provides an analysis of the Internet market in Germany, its potential for future growth in the wake of IPv4 run-out, and its relationship to the global Internet, drawing on data collected from a variety of RIPE NCC Internet measurement tools. We hope that these findings will help inform discussion, provide technical insight, and facilitate the exchange of information on Internet-related developments in Germany – particularly as the Internet Governance Forum (IGF) officially kicks off today in Berlin. You can also follow our liveblog of the IGF on RIPE Labs: https://labs.ripe.net/Members/gergana_petrova/igf-2019-liveblog If you find the report useful, please consider sharing it with your network. If you want to know more about the report or share feedback, we would very much like to hear from you at: <externalrelations(a)ripe.net> Best regards, Suzanne Taylor RIPE NCC

1 0

The RIPE NCC has run out of IPv4 Addresses
by Nikolas Pediaditis 25 Nov '19

25 Nov '19

Dear colleagues, Today, at 15:35 UTC+1 on 25 November 2019, we made our final /22 IPv4 allocation from the last remaining addresses in our available pool. We have now run out of IPv4 addresses. Our announcement will not come as a surprise for network operators - IPv4 run-out has long been anticipated and planned for by the RIPE community. In fact, it is due to the community's responsible stewardship of these resources that we have been able to provide many thousands of new networks in our service region with /22 allocations after we reached our last /8 in 2012. ---------------------------------------------------------------- Recovered IPv4 Addresses and the Waiting List ---------------------------------------------------------------- Even though we have run out, we will continue to recover IPv4 addresses in the future. These will come from organisations that have gone out of business or whose LIR accounts are closed, or from networks that return addresses they no longer need. They will be allocated to our members according to their position on a new waiting list that is now active. While we therefore expect to be allocating IPv4 for some time, these small amounts will not come close to the many millions of addresses that networks in our region need today. Only LIRs that have never received an IPv4 allocation from the RIPE NCC (of any size) may request addresses from the waiting list, and they are only eligible to receive a single /24 allocation. LIRs that have submitted an IPv4 request can see their position on the waiting list in the LIR Portal. A new graph has also been published that shows the number of requests on the waiting list and the number of days that the LIR at the front of the queue has been waiting: https://www.ripe.net/manage-ips-and-asns/ipv4/ipv4-waiting-list ---------------------------------------------------------------- Call for Greater Progress on IPv6 ---------------------------------------------------------------- This event is another step on the path towards global exhaustion of the remaining IPv4 addressing space. In recent years, we have seen the emergence of an IPv4 transfer market and greater use of Carrier Grade Network Address Translation (CGNAT) in our region. There are costs and trade-offs with both approaches and neither one solves the underlying problem, which is that there are not enough IPv4 addresses for everyone. Without wide-scale IPv6 deployment, we risk heading into a future where the growth of our Internet is unnecessarily limited - not by a lack of skilled network engineers, technical equipment or investment, but by a shortage of unique network identifiers. There is still a long way to go, and we call on all stakeholders to play their role in supporting the IPv6 roll-out. At the RIPE NCC, we are here to support our membership and the wider RIPE community in this work. Aside from allocating the IPv6 resources that will be required, we will continue to provide advice, training, measurements and tools to help network operators as they put their deployment plans into action. We are optimistic and excited to see what the next chapter will bring. So let's get to work - and together, let's shape the future of the Internet. Best regards, Everyone at the RIPE NCC

1 0

Volunteer for the RIPE Nominating Committee: In Conversation with Daniel Karrenberg
by Mirjam Kuehne 25 Nov '19

25 Nov '19

Dear colleagues, Do you have what it takes to volunteer for the RIPE Nominating Committee? In this article on RIPE Labs, we talk with Daniel Karrenberg, Chair of the 2019-2020 NomCom, about how you can get involved and what getting involved, actually means: https://labs.ripe.net/Members/elena_signorelli/volunteer-for-the-ripe-nomin… Kind regards, Mirjam Kühne RIPE NCC

1 0

Update: IPv4 Pool Runnning Low - Waiting List Published
by Nikolas Pediaditis 22 Nov '19

22 Nov '19

Dear colleagues, With less than 100 IPv4 /22-equivalents remaining in our pool, we expect that we will announce run-out early next week. Ahead of this, we have published a table and graph which will show the number of /24 requests when the waiting list becomes active (both the table/graph will obviously remain at zero until then). You can find this here: https://www.ripe.net/manage-ips-and-asns/ipv4/ipv4-waiting-list Because of the way we have implemented the waiting list, there is a small chance that some people will know we have reached IPv4 run-out before we do. While this is not overly important, to avoid confusion we thought it might be worth explaining why this could happen. To ensure fairness, each request effectively "reserves" a /22 until the allocation can be made. Depending on the rate of IPv4 requests, it's possible that we might end a workday with only a handful of /22s remaining in our pool. If the number of requests we receive outside of office hours exceeds the number of remaining allocations, any further requests will be added to the waiting list automatically. This will generate an email notification for the LIR that submitted the request - thereby informing them that we are out of /22 allocations. Of course, we would not have "officially" run out, as we would still have some (at least one) /22s waiting to be allocated when we returned to the office. We will make our announcement only once we have made the final /22 allocation. Kind regards, Nikolas Pediaditis Registration Services and Policy Development Manager RIPE NCC

1 0

New on RIPE Labs: How Far We've Come (In Conversation with Axel Pawlik)
by Mirjam Kuehne 19 Nov '19

19 Nov '19

Dear colleagues, At RIPE 79, precisely on the 20th anniversary of his taking charge at the RIPE NCC, Axel Pawlik announced that he would be stepping down. In his last week at the office, Axel shared some of his thoughts, looking back at his two decades as Managing Director of the RIPE NCC: https://labs.ripe.net/Members/ulka_athale_1/how-far-weve-come Kind regards, Mirjam Kühne RIPE NCC

1 0