- ripe-list - mailman.ripe.net

Ongoing discussion of RIPE Chair & Vice Chair selection by Nominating Committee
by Hans Petter Holen 30 Aug '19

30 Aug '19

I would like to draw your attention to the ongoing discussion on the ripe-chair-discuss list. The proposals were discussed in the BOF last night and there were good support in the room for the latest version. You can find the archives at: https://www.ripe.net/ripe/mail/archives/ripe-chair-discuss/2019-May/thread.… The latest version of the two proposals are at The Chair Selection Process https://www.ripe.net/ripe/mail/archives/ripe-chair-discuss/2019-May/000262.… The RIPE Nominating Committee https://www.ripe.net/ripe/mail/archives/ripe-chair-discuss/2019-May/000263.… Please join the discussion at the ripe-chair-discuss list. https://lists.ripe.net/mailman/listinfo/ripe-chair-discuss When the discussion phase has completed I will initiate a last call on this list, before declaring consensus. Hans Petter Holen RIPE Chair -- -- Hans Petter Holen Mobile +47 45 06 60 54 | hph(a)oslo.net | http://hph.oslo.net

13 17

RIPE 78 - The big picture
by Hans Petter Holen 30 Aug '19

30 Aug '19

I have, with the help of RIPE NCC published a RIPE Labs article with some of the key events and discussions from the meeting week. A lot goes on at a RIPE Meeting, so not everything is mentioned here, but it may serve as a short read preparing for the upcoming RIPE meeting in Rotterdam. https://labs.ripe.net/Members/hans_petter_holen/ripe-78-the-big-picture -- Sincerely, Hans Petter Holen - hph(a)oslo.net - +47 45066054

1 0

Second call for presentations RIPE 79
by Franziska Lichtblau 27 Aug '19

27 Aug '19

Dear colleagues, A list of currently accepted RIPE 79 presentations is now published at: https://ripe79.ripe.net/programme/meeting-plan/plenary/ There are still plenary, BoF, tutorial and workshop slots remaining for the final RIPE 79 programme and RIPE Programme Committee will accept new proposals until *8th September 2019*. Please note, that all the submissions we already received and did not explicitly accept or reject are still under consideration for the plenary at RIPE 79. Authors of accepted or rejected presentations have been contacted by the PC via the contact address they provided. You can find the CFP for RIPE 79 below or at https://ripe79.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings, see the "Speakers" paragraph in CFP for more information. Kind regards, Franziska Lichtblau RIPE PC Chair https://ripe79.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 79 will take place from 14-18 October in Rotterdam, The Netherlands* 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 79. See the full descriptions of the different presentation formats: https://ripe79.ripe.net/submit-topic/presentation-forma ts/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *16 August 2019*. 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 at 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://ripe79.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://ripe79.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe79.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://ripe79.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/ripe-meeting-code-o…

1 0

*2 days left to apply* - RIPE Fellowship at RIPE 79
by Amanda Gowland 05 Aug '19

05 Aug '19

Hi all, The deadline for the RIPE Fellowship at RIPE 79 in Rotterdam (14-18 October 2019) is *Wednesday, 7 August at 00:00 UTC*. The RIPE Fellowship offers successful candidates funding for travel, hotel and a full-week meeting ticket (including the RIPE Dinner). You must reside in the RIPE NCC service region for consideration (Europe, the Middle East and parts of Central Asia). Apply at: https://www.ripe.net/participate/ripe/ripe-fellowship The RIPE Fellowship is just one of the many ways we are increasing diversity and inclusion in the RIPE community. Read more about our D&I efforts: https://ripe79.ripe.net/diversity/ Kind regards, Amanda On behalf of the RIPE Fellowship Selection Committee

1 0

Deadline Extended: ASO AC Call for Nominations for the ASO Representative on ICANN NomCom
by Antony Gollan 02 Aug '19

02 Aug '19

This message is sent on behalf of the Number Resource Organization (NRO). Note: the call for nominations has been extended because an earlier notification was not sent to this mailing list. We apologise for the oversight. The Address Supporting Organization Address Council (ASO AC) has extended the deadline for nominations for the ASO Representative on the ICANN NomCom. New Deadlines and Important Dates --------------------------------- The ASO AC will be responsible for the selection of the delegate based on the following timeline: Nomination period ends: 9 August 2019 Evaluation of nominations by the ASO AC: 9 – 14 August 2019 ASO AC Voting period 15 - 21 August 2019 Announcement of selected delegate: 22 August 2019 All nominations should be sent to <secretariat(a)aso.icann.org> by 9 August 2019 23:59 UTC. Further Information ------------------- ICANN’s Nominating Committee (NomCom) is responsible for the selection of eight ICANN Board Members, two directors of the Public Technical Identifiers (PTI) and for other selections as are set forth in the Bylaws (see Article 8, Section 8.1). The NomCom is also charged with appointing some members of the ALAC, ccNSO Council and the GNSO Council. The NomCom complements the other means for filling a portion of key ICANN leadership positions achieved within the SOs and ACs. As per the ICANN Bylaws (Article 8, Section 8.2), the ASO AC is pleased to invite nominations for candidates from the “Internet Numbers Community” to run for an open seat on the ICANN NomCom 2020 as delegate of the ASO. The term for the selected delegate will be one year starting in ICANN 66 in Montreal, Canada, in November 2019 (see Article 8, Section 8.3 for term limits). All ICANN Bylaws described above can be found at: https://www.icann.org/resources/pages/governance/bylaws-en/#article8 Time Commitment for the ASO NomCom Representative ------------------------------------------------ The person should be able to join monthly teleconferences (typically 15:00 or 16:00 UTC). Note that the committee’s workload will increase significantly during Apr/May/June 2020 when the candidate assessment process will be at its busiest. Conference calls are held more frequently (typically weekly and the duration of the calls may last up to 3 hours) during this time. The person should be able to join (in person), three ICANN (66, 67 and 68) meetings and an intersessional meeting (location decided by NomCom 2020). Travel support for all meetings is provided by ICANN. The person must be able to attend the NomCom selection meeting in late June 2020 during ICANN 68. The ICANN NomCom has a set of guidelines and procedural documents for reference that provide additional information about the work of the NomCom. Regards Antony Gollan Senior Communications Officer RIPE NCC

1 0

Reminder: RACI Call for Applications Close on 7 August
by Gergana Petrova 31 Jul '19

31 Jul '19

Dear colleagues, This is the final call for applications for the RIPE Academic Cooperation Initiative (RACI). Applications from students, academics and researchers are accepted until *Wednesday, 7 August*. Successful applicants receive complimentary tickets, travel and accommodation to the meetings and the opportunity to present their research. https://www.ripe.net/raci Submit an abstract and draft slides to apply for the following two meetings: - RIPE NCC Regional Meeting (24-25 September, Kyiv) - RIPE 79 (14-19 October, Rotterdam) Examples of relevant research topics include: - Network measurements and analyses - IPv6 deployment - BGP routing - Network security - Internet governance - Peering and interconnectivity - Internet of Things RACI mailing list: https://www.ripe.net/raci/mailing-list Twitter: https://twitter.com/ripencc RACI LinkedIn Group: https://www.ripe.net/raci/linkedin For any questions about the initiative or about applying, please email me back. Best regards, Gergana Gergana Petrova External Relations RIPE NCC

1 0

Call for volunteers & Draft charter - RIPE Database Requirements Task Force
by Hans Petter Holen 25 Jul '19

25 Jul '19

I would like to call for volunteers for a task force of 2-5 persons to review the RIPE Database requirements. Please drop me an email if you have suggestions or would like to volunteer. The outcome of the task force will of course be discussed by the community to establish consensus as described below.. The RIPE Database has been discussed at the last couple of meetings and while we have a database working group dealing with technical details it has become clear that a wider discussion in the RIPE community is needed. The database is fundamental to the work of RIPE. There are questions about what kinds of data it should contain, what degree of accuracy is required, and what purposes it should be geared towards. These broad questions are not easily be answered with a policy proposal. Participants in the BoF at the last RIPE meeting supported the creation of a task force that would develop a set of requirements, considering what the RIPE Database needs to do and what information is required. Daniel has been kind to draft a charter for the task force, which I belive is a good start for the work: # RIPE Database Requirements Task Force Daniel Karrenberg *Version 1.1* ### Rationale The RIPE Database is now almost 30 years old [[ripe-13]] (https://www.ripe.net/publications/docs/ripe-013 "RIPE Databases"). During all this time, the community has developed the functionality of the Database incrementally. Today some new frictions have emerged such as changing privacy requirements and the use of the RIPE DB by parties outside the traditional community, specifically law enforcement. Because of these frictions and changing needs, the community consensus about the functionality of the RIPE DB has become less obvious. Therefore it is now time to take stock and to establish a clear consensus about what functionality the RIPE DB should provide in the future. ### Charter The RIPE Database Requirements task force shall develop a RIPE document listing all the [requirements] (https://en.wikipedia.org/wiki/Requirements_engineering "Wikipedia") for the RIPE DB and their rationales. The task force is a small and focused drafting team of two to five persons and not a representative body. The task force will consult the RIPE community and other interested parties. Consensus building will take place in the appropriate RIPE working groups and possibly specific BoFs. The task force will regularly publish draft versions of the document. ### Document Scope The purpose of the document is to establish community consensus at the general level. The document will be the new requirements specification for the RIPE DB. It shall provide clear guidance for the evolution of RIPE DB functionality, including the removal of current functionality that is no longer required. The document will prioritise requirements as much as possible. The document shall list the purpose of each RIPE DB function and consider the relevant privacy aspects, making the document useful in the context of privacy regulations such as the GDPR. The document shall allow easy updates as community needs change. Software development, deployment and other implementation details are out of scope. Despite being scoped as a requirements document, the document shall not prescribe a specific engineering methodology for subsequent steps in the process. ### Methodology The RIPE Chair shall appoint the task force after a call for volunteers. Volunteers are expected to contribute significant amounts of text and to collect community feedback. The task force will regularly publish revised drafts based on this feedback. The task force may conduct BoF sessions to discuss drafts with the community. ### Time Line The task force will start its work at [RIPE 79] (https://ripe79.ripe.net/ "RIPE 79, 14-18 October 2019") and produce the *first* draft by December 2019. The task force will deliver a document for last-call at RIPE 81 in October 2020. If the community does not achieve consensus by RIPE 81, the task force will give a report listing the open issues and propose a plan to resolve them.

1 0

Endorsement of Afrinic board candidates
by Sander Steffann 05 Jul '19

05 Jul '19

Hi RIPE ASO/AC delegates, I just read the following on the Afrinic community mailing list, and got a bit concerned: > My name is Wafa Dahmani from Tunisia, an active member of the African community and more specifically AFRINIC: member of the appeal committee; ASO / AC excom member and Ex Chair of Governance Committee '(GC) at AFRINIC. > I contact you to solicit your votes for the following candidates: > [etc] While she doesn't explicitly state that she is soliciting votes on behalf of the ASO/AC, it does seem to imply it. I found it hard to believe that the ASO/AC would agree with this statement as sent by Wafa. I know questions about this have already been sent to the ASO/AC, but I would like some feedback from our own delegates. I wonder whether you were aware of this and what your positions on this are. I suspect that this was not something agreed to by the ASO/AC, or at least not by our own delegates, but I would like that confirmed please :) I though long whether to cross-post this to the ripe-list and in the end decided that I should, for transparency's and accountability's sake. Cheers, Sander

4 7

New RIPE Document: RIPE Accountability Task Force Final Report
by Antony Gollan 04 Jul '19

04 Jul '19

Dear colleagues, The final report of the RIPE Accountability Task Force is now published as a RIPE Document. The document is available here: https://www.ripe.net/publications/docs/ripe-723/ Kind regards Antony Gollan Senior Communications Officer RIPE NCC

2 1

Re: [ripe-list] Endorsement of Afrinic board candidates
by Sander Steffann 03 Jul '19

03 Jul '19

Hi Hervé, > Thanks for sharing, we discovered today. In that case you have already answered the main part of my question :) If it was only discovered today then this can't have been agreed to by the ASO/AC :) Cheers, Sander

1 0