From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Fwd: [Battlemesh] REMINDER: call for papers for 2nd International Workshop on Community Networks and Bottom-up-Broadband (CNBuB2013)
Date: Thu, 9 May 2013 12:59:46 -0700 [thread overview]
Message-ID: <CAA93jw4omVmE+ap4f5hXgxYpKQwxt-uhXueySMdsotQ7Nst1cQ@mail.gmail.com> (raw)
In-Reply-To: <CALCh5=fsT5F=-9Dd4oicxrd0zkGs2xkkkXdAss1YzmNJBT+5aw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2686 bytes --]
I am pleased to see attempts at rejoining the development and academic
communities like the below.
I was very happy to get the results I got from fq_codel and best effort
traffic I got on a four hop mesh at battlemesh. Less happy with the 802.11e
results. See slides 63 and 64 here:
http://huchra.bufferbloat.net/~d/talks/nec_fixing_wifi.pdf
If only something could be done to get ietf MANET back in touch with
reality... and I had time to write papers. If anybody else does...
submission deadline is fairly soon.
---------- Forwarded message ----------
From: Roger Baig Viñas <roger.baig@gmail.com>
Date: Thu, May 9, 2013 at 9:02 AM
Subject: [Battlemesh] REMINDER: call for papers for 2nd International
Workshop on Community Networks and Bottom-up-Broadband (CNBuB2013)
To: Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>
Dear battlemeshers,
This mail is to remind you that the call for papers period for 2nd
International Workshop on Community Networks and Bottom-up-Broadband
(CNBuB2013) [1] is opened until June 15th.
As I already presented in a lighting talk in the WBMv6 last month [2]
this workshop is an effort to narrow the gap between community
networks and the academia. It is aimed to be a place for exchanging
knowledge and for exploring collaborations. We are convinced that
putting together the wide field experience and the innovative ideas
and proposals of the communities with the research resources and
methodologies of the academia must be beneficial for both sides.
Unfortunately academic conferences are not cheap, but we don't want
the cost to be an inconvenient for any community member to not submit
a paper. We have gathered some budget to sponsor (at least partially)
traveling costs and registration fees. Please send me an e-mail if you
need financial assistance.
This is the second edition of the workshop, and if we want to keep it
in the future we must make sure that this edition is, at least, as
successful as the first one. So... we need papers to be submitted ;-)
Please to not hesitate to contact me if you need any further
information, want to make a suggestion, etc.
[1] http://research.ac.upc.edu/CNBuB2013/
[2]
http://www.battlemesh.org/BattleMeshV6/Agenda?action=AttachFile&do=view&target=LT09_CNBuB2013_WS.pdf
Looking forward to your papers,
Felix Freitag and Roger Baig
CNBuB2013 Chairs
--
roger
_______________________________________________
Battlemesh mailing list
Battlemesh@ml.ninux.org
http://ml.ninux.org/mailman/listinfo/battlemesh
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 3597 bytes --]
parent reply other threads:[~2013-05-09 19:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CALCh5=fsT5F=-9Dd4oicxrd0zkGs2xkkkXdAss1YzmNJBT+5aw@mail.gmail.com>]
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4omVmE+ap4f5hXgxYpKQwxt-uhXueySMdsotQ7Nst1cQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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