From: Marek Lindner <lindner_marek@yahoo.de>
To: battlemesh@ml.ninux.org, olsr-users@lists.olsr.org
Cc: Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr>,
T.Koziniec@murdoch.edu.au, David Murray <D.Murray@murdoch.edu.au>,
b.a.t.m.a.n@lists.open-mesh.org, M.Dixon@murdoch.edu.au
Subject: Re: [B.A.T.M.A.N.] [Battlemesh] Another peer-reviewed assessment of Babel, Batman and OLSR
Date: Mon, 15 Nov 2010 11:14:51 +0100 [thread overview]
Message-ID: <201011151114.52497.lindner_marek@yahoo.de> (raw)
In-Reply-To: <4CE08734.9010402@murdoch.edu.au>
Hi,
> We are happy to answer any questions people might have with that paper.
Quote from:
http://bridgingthelayers.org/docs/murray_routing.pdf
"Upon inspection of the BATMAN L2 and BATMAN L3
results, the only major performance difference between data
link layer routing and network layer routing is the packet
size. Data link layer routing protocols will not require a
network layer IPv4/IPv6 header and may therefore be smaller."
Please note that the packet size of the protocol packets might be of vital
importance to the IETF and IEEE but for the batman project that was a rather
insignificant side effect. Having full control over the traffic flowing through the
mesh was the main motivation to go down to layer 2. It allowed us to implement
things like broadcast support & broadcast optimization (ARQ), multicast
support & optimization, interface alternating (consult the second part of this
article: http://www.open-mesh.org/wiki/2010-06-13-wbm2010-bracciano), seamless
roaming for non-mesh participants.
Regards,
Marek
parent reply other threads:[~2010-11-15 10:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4CE08734.9010402@murdoch.edu.au>]
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=201011151114.52497.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=D.Murray@murdoch.edu.au \
--cc=Juliusz.Chroboczek@pps.jussieu.fr \
--cc=M.Dixon@murdoch.edu.au \
--cc=T.Koziniec@murdoch.edu.au \
--cc=b.a.t.m.a.n@lists.open-mesh.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