[ripe-list] Call for presentations RIPE80

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 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://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 at ripe.net.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: </ripe/mail/archives/ripe-list/attachments/20200116/319a4c01/attachment.sig>