Message-ID: <7a79630a-bc90-e201-0b10-049ae93dc678@mojatatu.com>
Date:   Mon, 16 Jan 2017 10:00:37 -0500
From:   Jamal Hadi Salim <jhs@...atatu.com>
To:     netdev@...r.kernel.org
Cc:     netfilter-devel@...r.kernel.org, netfilter@...r.kernel.org,
        info@...devconf.org, linux-wireless@...r.kernel.org,
        tech-committee@...devconf.org, David Miller <davem@...emloft.net>,
        Stephen Jaworski <jaws@...atatu.com>,
        Rob Echlin <rob@...lin.ca>, lwn@....net,
        "info@...dev01.org" <info@...dev01.org>,
        tech-committee@...devconf.org
Subject: ANNOUNCE: Netdev 2.1 Call For Proposals Opened!


Folks,

We are pleased to announce that the CFP for netdev 2.1 is now open.

Netdev 2.1 is a community-driven conference geared towards Linux
netheads. Linux kernel networking and user space utilization of the
interfaces to the Linux kernel networking subsystem are the focus.
If you are using Linux as a boot system for proprietary networking, then
this conference _may not be for you_.

Netdev2.1 will be held in Montreal April 6-8
For more details visit: www.netdevconf.org

Netdev 2.1 has a theme: IOT networking and DDOS.
Submissions in that area are highly encouraged.

Current topics include:

IOT networking.
DDOS.
Wireless.
Performance analysis and improvement.
Networking hardware and offload.
Netfilter.
Traffic control.
Different networking layers (L2/3, etc.).
Security.
Additional topics can be suggested.

Session submissions
--------------------

We encourage submission of paper and tutorial proposals, though we
*highly highly discourage* submission of recycled talks. Your proposals
will be evaluated by the technical committee that will provide prompt
feedback to you. If your proposal is approved, you will be requested to
submit your Camera-ready paper.
Unlike other conferences where only the schedule is announced,
proposals will be regularly announced as they get accepted on our 
website and on relevant lists and twitter.

Please stay within the relevant topic focus and tie to FOSS Linux
networking to make it easier for the technical committee to provide
quick feedback. In order to give a talk you must be registered.
If your proposal is accepted you will not be charged a conference fee
or your conference fee will be refunded to you when your talk gets
accepted.

Types of proposals
-------------------
1. BoF

This serves to carry out initial discussions on some topic without any
pre-planned agenda.  At least one person is responsible for introducing
the topic, chairing and moderating it.  You have to list a few people
that will be planning to participate in the discussion.  Expect people
from the public to participate actively in the discussions.

The lifetime of a BOF may be only one or two Netdev conference 
gatherings. We discourage perpetual BOFs. BoFs don't need to have an
existing networking subsystem or mailing list. BOFs also don't need to
strive to be upgraded to be a Workshop in the future. Their longevity
could only be one conference. The sitting format could vary and be
either lecture or round table format depending on the proposal.


2. Talk
At least one person (of possibly multiple authors) is responsible for
the presentation.  Details proposal/development plans to the public for
45 minutes.
A paper submission of the talk is expected (please use the provided
template). The paper has to be a minimum of two pages and not to exceed
10 pages  (not including the references).

3. Tutorial

This implies planned agenda too.
Introduces audience to a topic.
Includes practical examples on using the functionality.
Functionality should already be in mainline or at least have been posted
already.

4. Workshops

Workshops are centered around existing networking subsystems.
Workshops are intended to be an extension of the mailing list in the
sense that many times previous discussions from the mailing list (or
that could otherwise have happened there) are taken to the round-table
to simplify the decision-making process.

The networking subsystem maintainer(s) should at least prepare a
list of agenda items well before the workshop takes place to allow
participants to come prepared; this makes the discussions most
productive.
Sometimes brain-storming sessions will also be appropriate where
being prepared is less important, for example for discussions
around new user requirements this can be very valuable.

At the workshop meeting itself discussions prevail and notes are
later sent back to the mailing list; presentations are typically
- at the discretion of the chairs - only used where needed to
clarify a problem statement for discussion.

Submiting Proposals
-------------------

Your proposal must be sent to tech-committee@...devconf.org before
February 20, 2017 with the following format:

Title: Title of the proposal
Type: BoF, Talk, Tutorial.
Description: (350 words max).
Submitter names:
Estimated time: (talk = 45 minutes max., tutorial = 90 minutes max.).

Once your proposal is accepted, please prepare your paper based on the
conference  template (odt or latex).

How to submit your paper
------------------------

Once your proposal is accepted and you have been invited to submit a
paper, please send the paper to both info@...devconf.org and
tech-committee@...devconf.org.

Deadlines
---------
February 20, 2017 Call for proposals close
Paper submission for review  March 27, 2017
Slides submission April 3, 2017

How to submit your slides
-------------------------

If your slides of your talk are ready, please send the PDF to:
info@...devconf.org.


cheers,
jamal

Powered by blists - more mailing lists