[164451] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Updated CFP for RIPE 67

daemon@ATHENA.MIT.EDU (Filiz Yilmaz)
Fri Jul 12 05:23:40 2013

From: Filiz Yilmaz <koalafil@gmail.com>
Date: Fri, 12 Jul 2013 11:23:26 +0200
To: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


Dear colleagues,

RIPE PC is now also accepting "Workshop" proposals for RIPE 67.=20

Please find the updated CFP with pointers to all possible presentation =
formats below and at:
https://ripe67.ripe.net/programme/cfp/

Note that the deadline for submissions is still 4 August 2013.

Kind regards

Filiz Yilmaz
Chair, RIPE Programme Committee
http://www.ripe.net/ripe/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 67 will take place from 14-18 October 2013 in Athens, Greece.

The RIPE Programme Committee (PC) is now seeking content proposals from =
the RIPE community for the plenary session presentations, BoFs (Birds of =
a Feather sessions), panels, workshops, tutorials and lightning talks at =
RIPE 67. The PC is looking for presentations covering topics of network =
engineering and operations, including but not limited to:

	=95 IPv6 deployment
	=95 Managing IPv4 scarcity in operations
	=95 Commercial transactions of IPv4 addresses
	=95 Data centre technologies
	=95 Network and DNS operations
	=95 Internet governance and regulatory practices
	=95 Network and routing security
	=95 Content delivery
	=95 Internet peering and mobile data exchange

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.

The RIPE PC accepts proposals for different presentation formats, =
including plenary session presentations, tutorials, workshops, BoFs =
(Birds of a Feather sessions) and lightning talks. See the full =
descriptions of these formats at=20
=
https://ripe67.ripe.net/programme/i-want-to-present/presentation-formats/

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 =93lightning talks=94, which =
are selected immediately before or during the conference.

The following general requirements apply:

	=95 Proposals for plenary session presentations, BoFs, panels, =
workshops and tutorials must be submitted for full consideration no =
later than 4 August 2013, using the meeting submission system =
(https://ripe67.ripe.net/submit-topic/). Proposals submitted after this =
date will be considered on a space-available basis.

	=95 Lightning talks should also be submitted using the meeting =
submission system (https://ripe67.ripe.net/submit-topic/) and can be =
submitted just days before the RIPE Meeting starts or even during the =
meeting week. The allocation of lightning talk slots will be announced =
in short notice =96 in some cases on the same day but often one day =
prior to the relevant session.

	=95 Presenters should indicate how much time they will require. =
See more information on time slot allocations per presentation format =
(https://ripe67.ripe.net/programme/i-want-to-present/presentation-formats/=
)

	=95 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 the names of invited panelists, presenters and moderators.

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

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

------------------=

home help back first fref pref prev next nref lref last post