[NLNOG] 2nd call for presentations RIPE 73

[Benno Overeinder]

Dear colleagues,

Please note the approaching deadline of 28 August 2016 for RIPE 73
plenary programme submissions.

You can find the CFP for RIPE 73 below or at
https://ripe73.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.

Kind regards,

Benno Overeinder
RIPE PC Chair
https://www.ripe.net/participate/meetings/ripe-meetings/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 73 will take place from 24-28 October 2016 in Madrid, Spain.

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 73.
See the full descriptions of the different presentation formats,
https://ripe73.ripe.net/submit-topic/presentation-formats/.

Proposals for plenary sessions, BoFs, panels, workshops and tutorials
must be submitted for full consideration no later than 28 August 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
- Internet of Things (IoT)


Submissions

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,
https://ripe73.ripe.net/submit-topic/submission-form/.

- Lightning talks should also be submitted using the meeting submission
system (https://ripe73.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
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.

- 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
NLnet Labs
http://www.nlnetlabs.nl/