[ipv6-wg] Call for Papers: RIPE 67

All,

This call for papers was sent to the RIPE list yesterday, and thought it
might be of interest to participants in this working group. IPv6 is of
interest to everyone, so a lot of IPv6-related topics are appropriate
for the plenary... don't be afraid! :)

Cheers,

--
Shane 

Begin forwarded message:

Date: Thu, 6 Jun 2013 10:42:39 +0200
From: Filiz Yilmaz <koalafil at gmail.com>
To: "ripe-list at ripe.net" <ripe-list at ripe.net>
Subject: Call for Papers: RIPE 67


Dear colleagues,

Please find the CFP for RIPE 67 below.
Note that the deadline for submissions is 4 August 2013

Kind regards

Filiz Yilmaz
for the RIPE Programme Committee
http://www.ripe.net/ripe/meetings/ripe-meetings/pc


---------------------------------------------------

Call for Papers: RIPE 67

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 67 will take place on 14-18 October 2013 in Athens, Greece.

The RIPE Programme Committee (PC) is now seeking content proposals from
the RIPE community for the Plenary, BoF and Tutorial sessions at RIPE
67. 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 center technologies
- Network and DNS operations
- Internet governance and regulatory practices
- Network and routing security
- Content delivery
- Internet peering and mobile data exchange


Submissions

Attendees of the RIPE meetings 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 who are proposing a panel or BoF are encouraged to include
speakers from several (perhaps even competing) companies and/or a
neutral facilitator.

In addition to presentations selected in advance for the Plenary, the
RIPE PC also offers several time slots for “Lightning Talks” which are
selected immediately before or during the conference.

The following requirements apply:

- Proposals for Plenary talks, BoFs, Panels and Tutorials must be
  submitted for full consideration no later than 4 August 2013, using
  the meeting submission system at:

https://ripe67.ripe.net/submit-topic/

Proposals submitted after this date will be considered on a
space-available basis.

- Presenters should indicate how much time they will require (30
  minutes for Plenary talks is a common maximum duration, although some
  talks can be longer).

- Proposals for talks 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
  names of invited panelists, presenters and moderators.

- Due to potential technical issues, it is expected that most if not
  all presenters/panelists will be physically present at the RIPE
  meeting.

- Tutorials are sessions with educational content and are alotted about
  2 hours. 

- BOFs (Birds of a Feather sessions) are informal gatherings on topics
  of shared interest  among RIPE Meeting attendees. Technical
  facilities and logistical support are limited and provided based on
  best effort and availability.  

- Lightning talks should also be submitted using the meeting submission
  system. They must be short (10 minutes maximum) and often involve
  more timely topics. They can be submitted at any time. The allocation
  of lightning talk slots will be announced one day prior to the
  relevant session.

If you have any questions or requests concerning content submissions,
please email pc [at] ripe [dot] net.

------------------------------------------------------------  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ipv6-wg/attachments/20130607/ec0554bc/attachment.html>