- ripe-list - mailman.ripe.net

Call for Public Comments on the 2019 IANA Performance Matrix Summary Report
by Nurani Nimpuno 05 Feb '20

05 Feb '20

Dear colleagues, As you may be aware, as a result of the successful IANA Stewardship transition in 2016, the IANA Numbering Services are today being managed through an SLA between ICANN and the five RIRs. As part of the result of the IANA Stewardship transition, the IANA Numbering Services Review Committee (IANA RC) was established in 2016. The IANA RC is composed of representatives from each RIR region, and advises and assists the RIRs in the review of the IANA Numbering Services. The IANA services are today provided by Public Technical Identifiers (PTI), which publishes monthly performance reports on the IANA Numbering Services (https://www.iana.org/performance/numbers) Based on these monthly performance reports, the five RIRs have produced the 2019 IANA Performance Matrix Summary Report: https://www.nro.net/wp-content/uploads/2019-RIR-IANA-summary-report.pdf The IANA RC IANA 2019 performance report ----------------------------------- The IANA RC is now launching a public comment period of 30 days, seeking comments and input from the community on the IANA numbering services performance and the 2019 IANA Performance Matrix Summary Report. The IANA RC encourages all members of the Internet number community to review the public IANA Performance Matrix Summary Report. Comments on the IANA service performance should be sent to: iana-performance(a)nro.net The IANA RC will publish an annual report in March 2020, as advice to the NRO EC with its evaluation of the IANA Numbering services. The report will be based on the IANA Performance Matrix Summary Report, as well as any input gathered on the performance from the global number community. The public comment period ends on Friday, 4 March 2020 at 23:59 UTC. All public comments will be published on the IANA RC website, and will be considered as input to the final report by IANA. At the end of the 30-day public comment period, the IANA RC will meet and evaluate all input to the final report. The IANA RC report will be published on the IANA RC website: https://www.nro.net/iana-numbering-services-review-committee Kind regards, Nurani Nimpuno Chair, IANA Numbering Services Review Committee References: ----------- IANA Numbering Services Review Committee https://www.nro.net/iana-numbering-services-review-committee/ Public Technical Identifiers (PTI) https://pti.icann.org IANA Stewardship Transition Archive https://www.nro.net/internet-governance/iana/iana-stewardship-transition/ The SLA for the IANA Numbering Services https://www.nro.net/sla Number Community Proposal https://www.nro.net/crisp-final-proposal

1 0

RACI, RIPE and SEE Fellowships Deadline End of Week!
by Gergana Petrova 03 Feb '20

03 Feb '20

Dear colleagues, You have until *9 February* to apply for the following funding opportunities: ---- RACI ---- - RIPE NCC Day (29 April, Tashkent) - RIPE 80 (11-15 May, Berlin) - ENOG 17 (8-9 June, Moscow) The RIPE Academic Cooperation Initiative (RACI) is open to academics that are interested to present their Internet-related research at one of our meetings. ripe.net/raci --------------- RIPE Fellowship --------------- - RIPE 80 (11-15 May, Berlin) The RIPE Fellowship is open to anybody living in the RIPE NCC’s service region. ripe.net/fellowship -------------- SEE Fellowship -------------- - SEE 9 (7-8 April, Ljubljana) ripe.net/see-9/fellowship The SEE Fellowship is open to anybody living in SouthEast Europe. Successful applicants get: - A free ticket for the event - Economy travel to/from home country to the event - Free accommodation near the event venue Please feel free to share this email with others you know who may be interested in applying to one of these initiatives. Let me know if you have any questions. Best regards, Gergana -- Gergana Petrova External Relations RIPE NCC

1 0

Tribute to Bill Manning
by Christian Kaufmann 27 Jan '20

27 Jan '20

Dear colleagues, It was with great sadness that we found out about the passing of Bill Manning this weekend. Bill has played a hugely important role in the development of the Internet since the 1970s, and he has had a great impact on the work of the operator community globally. Since he started his work at Texas Instruments and from his time working with Jon Postel at ISI, Bill has been an innovative and charismatic figure in our community. His record of making a positive impact on various groups and communities such as the IETF, RSSAC, ICANN, NANOG, APRICOT and ARIN is a testament to his energy and enthusiasm for the Internet and the people who work in this sphere. He was instrumental in the set-up of AfNOG in Africa when this was a part of our own RIPE community. Bill was a major contributor to work in the DNS field and especially the Internet's root zones, and he operated the B-root server for many years. Daniel Karrenberg, Chief Scientist at the RIPE NCC, notes: "Bill has been a great asset to the operators of the DNS root name servers. He would often contribute original points-of-view and interesting ideas." >From the tributes to Bill that we've seen throughout our community, it is clear that this originality and constant ability to bring interesting ideas and good humour to his work will be remembered. We hope you will join us in offering our condolences to Bill's family, friends and colleagues at this time. Regards, Christian Kaufmann RIPE NCC Executive Board Chairman

1 0

New on RIPE Labs: Reporting Back From RIPE 79
by Mirjam Kuehne 20 Jan '20

20 Jan '20

Dear colleagues, After RIPE 78, Hans Petter Holen, the RIPE Chair, published an article with some of my takeaways from the meeting and received some positive feedback about that. Here is another update from the RIPE 79 meeting: https://labs.ripe.net/Members/hans_petter_holen/reporting-back-from-ripe-79 Kind regards, Mirjam Kühne Senior Community Builder RIPE NCC

1 0

Call for presentations RIPE80
by Franziska Lichtblau 16 Jan '20

16 Jan '20

Dear colleagues, Please find the CFP for RIPE 80 below or at: https://ripe80.ripe.net/submit-topic/cfp/. The deadline for submissions is *23 February 2020*. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. However, on an individual basis, participants can apply for a RIPE Fellowship or RACI, see the "Speakers" paragraph in CFP for more information. Kind regards, Franziska Lichtblau RIPE PC Chair https://ripe80.ripe.net/ripe-pc/ -------------------------------------------------------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. *RIPE 80 will take place from 11-15 May in Berlin, Germany* The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 80. See the full descriptions of the different presentation formats: https://ripe80.ripe.net/submit-topic/presentation-formats/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *23 February 2020*. Proposals submitted after this date will be considered depending on the slots still available in the programme. The PC is looking for presentations covering the topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) ---- Speakers ---- Presenters, RIPE Working Group Chairs and the RIPE Programme Committee are required to cover their own costs to attend a RIPE Meeting (meeting ticket, travel and accommodation). We have various ticket options available depending on your needs. Please note that participants can apply for a RIPE Fellowship or RACI, on an individual basis, to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship https://www.ripe.net/participate/ripe/raci In extraordinary circumstances, the RIPE Chair can waive the meeting fee for presenters. These requests are dealt with on a case-by-case basis via pc(a)ripe.net. ---- Submissions ---- Presenters should be clear on whether they wish to submit a presentation for a plenary or working group (WG) session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe80.ripe.net/plenary-or-wg/ RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and should not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour (during evening sessions) - Lightning talks: 10 minutes in total for both the presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe80.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe80.ripe.net/submit-topic/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. ---- Diversity and Inclusion - On-Site Childcare and the RIPE Meeting Code of Conduct ---- Did you know that RIPE Meetings now have on-site childcare? You can reserve a spot for your child (age 6 months - 10 years) during the registration process for the meeting. Childcare places are limited, so please be quick to reserve a spot for your child while registering for the meeting. More information at: https://ripe80.ripe.net/on-site/on-site-childcare/ Ensuring that RIPE Meeting values are upheld and that attendees experience a professional, respectful and safe meeting is a priority. Please do read the RIPE Meeting Code of Conduct: https://www.ripe.net/participate/meetings/ripe-meetings/ri pe-meeting-code-of-conduct --- If you have any questions or requests concerning content submissions, please [10]email pc(a)ripe.net.

1 0

RIPE NomCom Formed
by Daniel Karrenberg 14 Jan '20

14 Jan '20

The RIPE NomCom has now been formed and starts its work. Name Mailbox Comment --------------------------------------------------------- Voting Members Arnold Nipper arnold.nipper Benno Overeinder benno Dmitry Burkov dvburk Dmitry Kohmanyuk dk Gert Döring gert Joe Abley jabley Ondřej Caletka ondrej.caletka Robert Evans Rob.Evans also a liaison Sander Steffann sander Tina Morris Tinam Advisors Anna Wilson anna.wilson 'previous NomCom chair’ Daniel Karrenberg chair Liaisons Jan Žorž jan Programme Committee Piotr Strzyżewski Piotr.Strzyzewski RIPE NCC Board Robert Evans Rob.Evans RIPE WG Chairs Support Daniella Coutinho support clerical support role The 10 voting members will select the next RIPE Chair with support from the advisors and liaisons. Anna Wilson has agreed to fill the role of ‘previous NomCom chair’ in this very first RIPE NomCom. Committee members can receive NomCom related mail at their respective mailboxes at ripe-nomcom.org. The whole committee can be reached at the ‘nomcom’ mailbox. We will keep the community updated on our progress. Daniel Karrenberg Chair RIPE 2020 Nominations Committee

1 0

NomCom Volunteers and Selection
by Daniel Karrenberg 17 Dec '19

17 Dec '19

By the deadline these 36 people have volunteered for the RIPE Nominations Committee: 20 Alexander Isavnin Internet Protection Society 13 Andreas Wkittkemper Verizon Deutschland GmbH 24 Antonio Prado SBTAP 10 Arnold Nipper DE-CIX Management GmbH 21 Benno Overeinder NLnet Labs 23 Brian Nisbet HEAnet 31 Cosmin Octavian Lupu Visma 19 Dmitry Burkov RU-CENTER 25 Dmitry Kohmanyuk Hostmaster.UA 27 Frederic Jaeckel GitHub, Inc. 07 Geoff Huston APNIC 08 Gert Döring SpaceNet AG 09 Hervé Clément Orange SA 14 Jim Reid RTFM llp 15 Joe Abley Public Interest Registry 36 João luis silva damas APNIC 28 Keith Mitchell DNS-OARC 16 Marcus Stoegbauer Megaport / ECIX 29 Markus de Brün BSI 04 Martin Winter Network Device Education Foundation (Net 26 Massimo Candela NTT 17 Mircea Ulinic DigitalOcean 32 Nathalie Trenaman RIPE NCC 33 Nurani Nimpuno Asteroid International 11 Ondřej Caletka CESNET 18 Pascal Gloor Quickline AG 12 Paul Hoogsteder Meanie 06 Randy Bush Arrcus Inc & IIJ & RGnet 03 Robert Evans Jisc 02 Sander Steffann Global NOG Alliance 35 Shane Kerr NS1 34 Simone Ferlin Ericsson 05 Stefan Wahl Megaport / ECIX 30 Tina Morris Amazon 01 Wolfgang Tremmel DE-CIX Management GmbH 22 Wolfgang Zenker punkt.de GmbH This is about 10% of our estimate for the number of eligible persons. In the name of the RIPE community I thank all these people for volunteering. For 35 of them we have verified that they have attended at least three out of the five most recent RIPE meetings. The ten voting members of the NomCom will be selected by the method specified in RFC3797 based on the numbers in the list above and on the following lotto results of Wednesday, December 11th: Deutscher Lottoblock [https://www.lotto.de/lotto-6aus49/lottozahlen] Swisslotto [https://www.swisslos.ch/de/swisslotto/information/gewinnzahlen/gewinnzahlen…] Österreichische Lotterien [https://www.win2day.at/lotterie/lotto] In the event this method will select a person whose eligibility is not yet confirmed or a person who does not re-confirm their willingness to serve, the next person in the sequence will be selected and so forth. Daniel Karrenberg Chair of the RIPE Nominations Committee PS: In an earlier statement I said that I would use the Luxembourg Lotto. During a trial run today however it became obvious that they are very pragmatic and use the numbers of the German lotto. ;-) In order to have ample entropy I chose to use the Austrian lotto instead.

7 14

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