- ripe-list - mailman.ripe.net

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

ASO Use of Empowered Community Powers for ICANN Fundamental Bylaw Change
by Antony Gollan 15 Nov '19

15 Nov '19

This message is sent on behalf of the Number Resource Organization (NRO). ASO Use of Empowered Community Powers for ICANN Fundamental Bylaw Change On 13 September 2019, the NRO (fulling the role of the Address Supporting Organization – ASO) received an ICANN Board Notice of Board Approval of Fundamental Bylaws Amendment regarding the IANA Naming Function Review Composition. The notice states: “Moving forward with the Fundamental Bylaws Amendment Process is in direct response to the request of the ccNSO Council, and also supports the new accountability and oversight mechanisms designed by the community in the IANA Stewardship Transition Process. The IANA Naming Function Review is an important part of the accountability and oversight of IANA’s performance of the Naming Function and was a key aspect of the Transition proposal. During the pendency of Bylaws’ change process to date, the ccNSO Council was eventually able, through considerable effort and perseverance, to locate a non-ccNSO member ccTLD manager to serve on the current IANA Naming Function Review Team. However the ccNSO Council is likely to be unable to complete the required composition of the IANA Naming Function Review Teams in the future unless we continue with this change. Taking this action today is a step forward to making sure that the IANA Naming Function Reviews can proceed in a manner that the ICANN community collectively supports, as will be identified through the Fundamental Bylaws process.” https://www.icann.org/en/system/files/bm/secretarys-notice-3-13sep19-en.pdf On 3 November 2019, there was an Approval Action Community Forum (during ICANN’s 66th public meeting in Montreal) related to this proposed Fundamental Bylaw amendment. In accordance with our role as a Decisional Participant in the Empowered Community, the NRO must consider this Fundamental Bylaws change. The NRO EC has reviewed the proposed change and believes that this ICANN Bylaws change does not impact the Internet numbers community and allows ICANN to remain accountable to its Bylaws-mandated mechanisms. Intention to Support The NRO, in keeping with its adopted ASO Procedures for ICANN Empowered Community Powers, is informing the Numbers community of completion of the community forum at ICANN 66 and the NRO’s intention to support this approval action petition. Community members that wish to provide feedback on the intended action may email comments to <secretariat(a)nro.net>. The NRO will consider input received by Monday 25 November, 2019 in making its final determination whether to support, oppose or abstain in this approval action process. Regards Antony Gollan Senior Communications Officer RIPE NCC

2 1

RIPE NomCom Deadline Extended
by Daniel Karrenberg 08 Nov '19

08 Nov '19

Dear colleagues, We have received 30 volunteers for the RIPE NomCom so far. This is a great start, but I believe we can do better. Therefore, after consulting with the RIPE Chair and the RIPE NCC Executive Board Chairman, I am extending the deadline for volunteering by two weeks, until Sunday, 1 December 2019 . The NomCom plays an essential role in the self-governance of our community by selecting the RIPE Chair and Vice Chair. As such, it is important that the NomCom members are selected from a diverse pool of initial volunteers. As this is a new process, we also need to ensure that everyone is aware of what the NomCom does and how its members are randomly selected. We have had excellent leadership from both Rob and Hans Petter to date, but RIPE cannot rely on good fortune to ensure this remains the case. If you consider yourself a member of this community, please support the process - either by volunteering yourself or encouraging others to step forward as potential NomCom members. For details see the message below. Daniel Karrenberg Chair of the 2019-2020 RIPE NomCom —— Dear RIPE Participant, RIPE will choose its next chair and a vice chair by way of a nominations committee. Ten volunteers, randomly selected from the community, will make that choice with the help of the whole community. These ten people plus a number of non-voting liaisons and advisors will form the NomCom. The NomCom will start to work around January 2020 and make its selection soon after the next RIPE meeting in May of that year. The job of the NomCom is to select people who have what it takes and also have the support of the community. As chair of the 2019-2020 Nomcom, my job is to organise the work and help the volunteers with making their choice. Therefore I call on you to volunteer. Ideally we are looking for about 100 volunteers representing a broad range of RIPE participants. Ten of those people will be randomly selected to serve on the NomCom. To qualify for serving as a voting volunteer you have to have attended three of the five most recent RIPE meetings up to the meeting taking place this week in Rotterdam. For details about the procedures and duties of the NomCom you may refer to documents ripe-727 and ripe-728. The deadline for volunteering is Sunday November 10th 2019. The only way to volunteer is by using the form at https://www.surveymonkey.com/r/ripenomcom Daniel Karrenberg Chair of the 2019-2020 RIPE NomCom

1 0

RACI: Call for Applications
by Gergana Petrova 05 Nov '19

05 Nov '19

Dear colleagues, The RIPE Academic Cooperation Initiative (RACI) is again looking for talented academics in the field of Internet technology. Successful applicants receive complimentary tickets, travel and accommodation to the meetings and the opportunity to present their research. If you are working on something interesting, please apply! If you know someone in your network who is, please forward them this message. To apply submit a short abstract and draft slides via: https://www.ripe.net/raci --------------------- Application deadlines --------------------- MENOG 20 (15-19 March, Manama): apply by 19 January 2020 SEE 9 (7-8 April, Ljubljana): apply by 19 January 2020 RIPE NCC Day (29 April, Tashkent): apply by 9 February 2020 RIPE 80 (11-15 May, Berlin): apply by 9 February 2020 ENOG 17 (8-9 June, Moscow): apply by 9 February 2020 At ENOG 17 and the RIPE NCC Day in Tashkent you can present in either Russian or English. --------------------------- Examples of relevant topics --------------------------- - Network measurements and analyses - IPv6 deployment - BGP routing - Network security - Internet governance - Peering and interconnectivity - Internet of Things ------------------------------------------------- Get the latest news on RACI and Internet research ------------------------------------------------- - Subscribe to the RACI mailing list: https://www.ripe.net/raci/mailing-list - Join our group on LinkedIn: https://www.ripe.net/raci/linkedin Please let me know if you have any questions. Have a lovely day! Best regards, Gergana -- Gergana Petrova External Relations RIPE NCC @_GeriPetrova

1 0

Call for Volunteers to Serve on the 2019-2020 RIPE NomCom
by Daniel Karrenberg 28 Oct '19

28 Oct '19

Dear RIPE Participant, RIPE will choose its next chair and a vice chair by way of a nominations committee. Ten volunteers, randomly selected from the community, will make that choice with the help of the whole community. These ten people plus a number of non-voting liaisons and advisors will form the NomCom. The NomCom will start to work around January 2020 and make its selection soon after the next RIPE meeting in May of that year. The job of the NomCom is to select people who have what it takes and also have the support of the community. As chair of the 2019-2020 Nomcom, my job is to organise the work and help the volunteers with making their choice. Therefore I call on you to volunteer. Ideally we are looking for about 100 volunteers representing a broad range of RIPE participants. Ten of those people will be randomly selected to serve on the NomCom. To qualify for serving as a voting volunteer you have to have attended three of the five most recent RIPE meetings including the meeting taking place this week in Rotterdam. For details about the procedures and duties of the NomCom you may refer to https://www.ripe.net/publications/docs/ripe-727 and https://www.ripe.net/publications/docs/ripe-728. The deadline for volunteering is Sunday November 10th 2019. The only way to volunteer is by using the form at https://www.surveymonkey.com/r/ripenomcom Daniel Karrenberg Chair of the 2019-2020 RIPE NomCom

2 2

RIPE 79 thank you
by Hans Petter Holen 26 Oct '19

26 Oct '19

Dear colleagues, The RIPE 79 Meeting in Rotterdam came to a successful end last Friday. I'd like to thank all of you that took part in the meeting on site and remotely. It was a very successful RIPE Meeting with 736 attendees checked in, from 59 countries, 187 of whom were joining us for the first time. This time, we celebrated 10 years of RIPE Labs, kicked off the RIPE Chair election process at the RIPE community plenary, and said farewell to Axel Pawlik, RIPE NCC Managing Director, who announced that he will step aside for a new generation of leaders after 20 years of service. We also discussed the IPv4 run-out and what it means for you, the update on the Code Of Conduct (CoC), and the upcoming launch of the Certified Professionals Programme. At the meeting, we received a lot of valuable feedback from you. The meeting organising team is now reviewing the completed forms and will make sure that actions are taken where possible. You can read the meeting report at: https://ripe79.ripe.net/programme/report/ Archives of all the meeting's presentations are online: https://ripe79.ripe.net/archives/ RIPE 80 will take place in Berlin, Germany from 11-15 May 2020: https://ripe80.ripe.net/ See you soon! Best regards, Hans Petter Holen RIPE Chair

1 0

CoC and RIPE meetings
by Sascha Luck [ml] 22 Oct '19

22 Oct '19

WARNING: This post contains IRONY and, despite great care having been taken in producing it, may contain traces of SARCASM! RIPE meetings, at least to me, have become more boring and unedifying since my first one (pretty sure it was RIPE-32). This CoC is a great idea to make those meetings more interesting again. It creates an opportunity to play a number of thrilling and exciting games: RIPE::Moscow Rules - Spot the Informer: Look around you in sessions and at lunch! Can you spot the CoC-Stasi? - Countersurveillance: Spot and evade surveillance by making Surveillance Detection Runs through the meeting venue! - Clandestine Comms: Communicate covertly with other Dissidents! Use dead drops, brush passes and encrypted wifi! - Busted: Tell a joke to someone you trust and find out they've been working for the Stasi all along! - Do Unto Others: Report your colleague before they report you! Prizes: If you make it to Friday without being reported to the CoC-Stasi, you may come back to play at the next meeting. If not, you are burned and banned from playing. But do not despair: you can still try and play again at PRO level: - Incognito: Construct your legend and use it to try to infiltrate a meeting despite having been burned before! Hell I might even go to a meeting again myself and try my hand at tradecraft! All humour aside: Abolish RIPE meetings. They do not serve any purpose (anymore) that cannot be served online more easily and less expensively. The NCC has budgeted a cool EUR 2.18 million for meetings in 2020[1] That is a rough EUR100 per member now and likely to be significantly more in the future. They are also, as we have been told again and again, horrible events, attended by monsters, where nobody in their right mind wants to go. I really don't know why any member should want to pay for *that* So abolish them. That should also obviate the need for a Code Of Conduct and its enforcers. rgds, Sascha Luck [1] https://www.ripe.net/participate/meetings/gm/meetings/october-2019/draft-ri…

2 1

CoC and the PDP
by Sascha Luck [ml] 21 Oct '19

21 Oct '19

All, the CoC draft version 3.0 [1], while it is called the "RIPE Meeting Code of Conduct", makes reference to the PDP as detailed below. - in "Scope" it claims authority over "RIPE mailing lists and the RIPE Forum" - "In cases where a report involves a RIPE Working Group Mailing List, the RIPE CoC Team will consult with the respective RIPE Working Group Chairs to gather context or any other relevant information that may help with its investigation." - One of the possible sanctions described is: "Not allowing someone to participate further in RIPE Meetings and/or *other RIPE community spaces*, for a set period or an indefinite period" Generally the tenor of the document is that, yes, it is intended to apply to the PDP-relevant processes and spaces and I don't think that fact is disputed. This is fundamentally incompatible with ripe-1 and ripe-710. If you, like me, consider those documents our "constitution", this CoC violates the letter as well as the spirit. If this reads like politics, that is because it *is*. 1) I consider ripe-1 and ripe-710 the "constitution" that provides for all of the below[2][3] 2) I consider the PDP and its WG mailing lists our "legislative". 3) The RIPE NCC could, in a very loose sense, be called our "executive". Like any democratic executive, it governs by the consent of the governed and is charged with implementing policy made through the PDP. 4) I consider the WG chair collective as some sort of combined "Speaker of Parliament", "Head of State" and "Constitutional Court". Their purpose is to steer the PDP and ensure that processes are followed in accordance to ripe-710 and ripe-1. They also determine that a consensus has been reached. (They "sign a proposal into law", so to speak.) 5) Through the PDP policy is developed, policy that affects every internet user in the RIPE Service Region. It affects more people and organisations than any law made even in the European Parliament. 6) According to ripe-710, the PDP is "open to all", "transparent", "from the bottom up" and "Conclusions are reached by consensus". To me, this means that every voice that wishes to speak must be heard. 7) Policy proposals, "bills" in other words, are often contentious, much like proposed law in other venues. Debate has, in the past, often been robust, raucous and occasionally vociferous. This is as it should be, this broad a community will rarely be of one mind and people have different ideas. Dissent, as in any democracy, is essential, even more so in a consensus-based system. How does the proposed CoC affect all this? For one, it is not transparent: Decisions are made behind closed doors, decisions that will - the draft document is clear on this - lead to voices being silenced and being silenced *silently*. It is not "open to all": it is only open to those who have not fallen afoul of the CoC or its enforcers. It is not consensus-based: "consensus of the approved" is worthless. It is not "bottom-up": the CoC Team sits at the very top of the chain and determines who can be a member of the RIPE community and who can't. Finally, it is open to abuse and, arguably, *designed* to be abused. It opens the way to anyone who is not happy ("comfortable" in the words of the draft) with the outcome or direction of a PDP discussion to rely on anonymous denunciation and intransparent processes to have all dissent silenced. The draft contains no reference to fairness or to a right of the accused to be heard and to defend themselves, which is a perversion of natural justice[4]. There is some kind of right-of-appeal, but it's an appeal to the same people who issued a "conviction" in the first place. Applied to the PDP and its participants, this, in political terms, is a putsch. It establishes a cabal that has the power to determine who may participate in the PDP in the first place. This may lead to the establishment of a sham consensus as all dissenting voices have been silenced, which the remaining community may not even be aware of. Policy developed under this system should be considered in violation of ripe-1 and ripe-710 and thus "unconstitutional". I'm not sure where the NCC stands in regard to obligations imposed on it by illegitimately created policy. This may be a question for the membership. There was a call for solutions, rather than just complaints, earlier. In this spirit I offer two possibilities: 1) Apply a "parliamentary privilege"[5] to PDP discussions. This means that only the WG chair collective has jurisdiction over PDP discussions and can "punish" participants - but with full transparency. 2) Let the "CoC team" investigate complaints but leave any decisions up to the WG chair collective. Again, any bans, temporary, or permanent must be fully transparent. As an aside, has anyone considered the difficulty of enforcing something like this on MLs where no identification requirement exists and someone "banned" can just re-sub under a different name/email address? In any case, I'd like to hear some discussion on this. Speak up. please. It may be the last chance you have. rgds, Sascha Luck [1] https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… [2] https://www.ripe.net/participate/meetings/roundtable/march-2005/presentatio… [3] https://www.ripe.net/publications/docs/ripe-710 [4] https://en.wikipedia.org/wiki/Natural_justice [5] https://en.wikipedia.org/wiki/Parliamentary_privilege

7 10

Towards a more inclusive community
by Job Snijders 21 Oct '19

21 Oct '19

Dear all, I've been observing various efforts towards constructing a safe and inclusive environment both at RIPE meetings and our online platforms. I appreciate these efforts, however, I have some concerns with the process and our ability to execute. A careful observer may see that the next generation of Internet engineers is not quite like the current establishment. I believe this diversity needs to be acknowledged in our policies. We owe it to them to create an environment that contributes to their comfort and well being. I recorded some thoughts on my way to RIPE - https://youtu.be/6_dLgcfv8kU Kind regards, Job

10 12