From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org,
"shantanoo_desai@hotmail.com" <shantanoo_desai@hotmail.com>
Subject: Re: [B.A.T.M.A.N.] Distributing Data using BATMAN-Multicast
Date: Fri, 17 Feb 2017 08:56:44 +0100 [thread overview]
Message-ID: <2164005.BaM7rbROku@bentobox> (raw)
In-Reply-To: <DB5PR09MB0391C18D43FB524CC828F191B35A0@DB5PR09MB0391.eurprd09.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Donnerstag, 16. Februar 2017 12:35:32 CET Shantanoo Desai wrote:
> I have developed a Multicast based Data Distribution protocol
[...]
> I would like to compare how quick can data be disseminated in a Batman
> enabled Mesh network versus the protocol that I have developed
You've already lost me here. You say that your protocol is a "data
distribution protocol" which is using multicast ("Multicast based"). But the
L2 multicast feature [1] of batman-adv is an optimization which tried to
reduce the amount of broadcasts on the underlying layer (for example wifi)
while still allow interested multicast listeners to receive the data. So you
could say that it "implements" L2 multicast in a slightly different way than
in older batman-adv versions (which was just using broadcasts on the
underlying layer).
So your description sounds to me like these things are two different things
for two different tasks. Basically two different layers in the stack. Can you
clarify this?
Kind regards,
Sven
[1] https://www.open-mesh.org/projects/batman-adv/wiki/Multicast-optimizations
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-02-17 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 12:35 [B.A.T.M.A.N.] Distributing Data using BATMAN-Multicast Shantanoo Desai
2017-02-16 13:38 ` dan
2017-02-16 14:33 ` Linus Lüssing
2017-02-17 7:56 ` Sven Eckelmann [this message]
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=2164005.BaM7rbROku@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=shantanoo_desai@hotmail.com \
/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