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 78.
Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 3 March 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)
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:
RIPE Fellowship and 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 [dot] net.
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, you may find it useful to check out further information on the difference between plenary and working group sessions.
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 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
- Lightning talks: 10 minutes
The following general requirements apply:
- Proposals must be submitted using the meeting submission system.
- Lightning talks should also be submitted using the meeting submission system 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.
- 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 panelists, presenters and moderators.
- Due to potential technical issues, presenters/panelists should be physically present at the RIPE Meeting.
Diversity and Inclusion at RIPE Meetings
Did you know that RIPE Meetings now have on-site childcare? We are making it easier for parents to fully participate in the meeting without having to stress about childcare.
Ensuring that RIPE Meeting values are upheld and that attendees experience a professional, respectful and safe meeting is a priority. Please be sure to read the RIPE Meeting Code of Conduct.