[ENOG discuss] Fwd: Call for presentations RIPE 72
sergey at devnull.ru
Wed Jan 27 16:35:13 CET 2016
RIPE 72 пройдет 23-27 мая в Копенгагене. Если у вас есть презентация, которую вы хотели бы
представить на RIPE Meeting - пожалуйста, изучите ниже приведенный call for presentationы
и отправьте вашу заявку через систему подачи заявок.
Если же у вас есть вопросы по любому аспекту докладов на RIPE Meeting - пожалуйста, спрашивайте меня.
From: Benno Overeinder <benno at NLnetLabs.nl>
To: ripe-list at ripe.net
Date: Monday, January 25, 2016, 11:07:56 PM
Subject: Call for presentations RIPE 72
===8<==============Original message text===============
Please find the CFP for RIPE 72 below or at
The deadline for submissions is 13 March 2016.
Please also note that speakers do not receive any extra reduction or
funding towards the meeting fee at the RIPE Meetings.
RIPE PC Chair
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 72 will take place from 23-27 May 2016 in Copenhagen, Denmark.
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 72.
See the full descriptions of the different presentation formats,
Proposals for plenary sessions, BoFs, panels, workshops and tutorials
must be submitted for full consideration no later than 13 March 2016.
Proposals submitted after this date will be considered depending
on the remaining available space in the programme.
The PC is looking for presentations covering topics of network
engineering and operations, including but not limited to:
- IPv6 deployment
- Managing IPv4 scarcity in operations
- Commercial transactions of IPv4 addresses
- Data centre technologies
- Network and DNS operations
- Internet governance and regulatory practices
- Network and routing security
- Content delivery
- Internet peering and mobile data exchange
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
- 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 (https://ripe72.ripe.net/submit-topic/submission-form/) 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
- Presenters who propose a panel or BoF are encouraged to include
speakers from several (perhaps even competing) companies and/or a
- 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.
- Due to potential technical issues, presenters/panellists should be
physically present at the RIPE Meeting.
If you have any questions or requests concerning content submissions,
please email pc [at] ripe [dot] net.
Benno J. Overeinder
===8<===========End of original message text===========
More information about the discuss