public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>,
	The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>,
	olsr-users@lists.olsr.org, babel-users@lists.alioth.debian.org
Subject: [B.A.T.M.A.N.] Wireless Battle Mesh v4 - Call for papers
Date: Fri, 21 Jan 2011 19:33:01 +0100	[thread overview]
Message-ID: <201101211933.03003.lindner_marek@yahoo.de> (raw)


Wireless Battle Mesh v4 - Call for papers
=========================

Wireless Battle Mesh v4 is at hand and it is time to bring together the 
agenda. To avoid last year's dynamic process which gave us a true talk 
marathon on the very last day of WBMv3 all talks / workshops / panel 
discussions shall be announced beforehand.


Tracks
====

In order to broaden the horizon of the event we are going to split the event 
into different tracks:

* The technical track is taking place throughout the week (monday till friday) 
which mainly focuses on rather technical topics like: 
 => routing protocol internals
 => implementations / development of "cool" algorithms
 => hands-on routing / multicast / roaming / convergence speed / etc
 => secuity aspects in mesh networks
 => your idea here

* The weekend (saturday & sunday) is reserved for the applications track which 
aims to showcase applications that run on top of the mesh. It is not important 
whether protocol X or Y is deployed and how it is implemented, the question 
is: What can we do with the mesh once it is there ?
 => VoIP in the mesh ?
 => fast desaster recovery ?
 => artistic projects ?
 => your idea here

The idea of these tracks is to provide a ground for the different developers / 
projects to exchange ideas on technical aspects of algorithms / 
implementations / optimizations as well as organizing an exchange with mesh 
network users who care less about how the mesh itself works as long as their 
application can do its job. On the other hand the weekend serves as an entry 
point for people to learn about what you can actually do with mesh networks.


Submission
=======

To allow an efficient handling of your submission, please provide the following 
information and send them to me directly in form of an email:

* your name
* the track you are interested in
* the type of your slot (talk/workshop/panel discussion)
* your topic headline
* your topic description which can brief (does not need to exceed a couple of 
lines) but should provide a reasonable summary of your talk
* the dates of your stay at the event + (optional) preferred day for your slot
* length of the slot if you wish to do a workshop (all other slots will be 
limited to one hour - notify me in advance if you think that is not enough for 
you)


Deadlines
======

Submissions are accepted until and including the 28th of February. Everyone 
missing this deadline still has the opportunity to apply for a lightening talk 
slot. These slots can be acquired by simply contacting me during the event. 
The list of registered lightening talks will be published in the battlemesh 
wiki.
The final program will be made available in the aforementioned wiki during the 
first week of March.

If you have any question or suggestion, please let me know.

Regards,
Marek


             reply	other threads:[~2011-01-21 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 18:33 Marek Lindner [this message]
2011-01-23  7:44 ` [B.A.T.M.A.N.] [Babel-users] Wireless Battle Mesh v4 - Call for papers Gabriel Kerneis
2011-01-23 11:28   ` elektra
2011-01-23 12:16   ` Mitar
2011-02-07 14:50 ` [B.A.T.M.A.N.] [Battlemesh] Wireless Battle Mesh v4 - Call for papers (update) Marek Lindner
2011-02-22 14:22   ` [B.A.T.M.A.N.] [Battlemesh] Wireless Battle Mesh v4 - Call for papers (update II) Marek Lindner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201101211933.03003.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=battlemesh@ml.ninux.org \
    --cc=olsr-users@lists.olsr.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox