From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: "shantanoo_desai@hotmail.com" <shantanoo_desai@hotmail.com>,
The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Distributing Data using BATMAN-Multicast
Date: Thu, 16 Feb 2017 15:33:48 +0100 [thread overview]
Message-ID: <20170216143347.GC24635@otheros> (raw)
In-Reply-To: <DB5PR09MB0391C18D43FB524CC828F191B35A0@DB5PR09MB0391.eurprd09.prod.outlook.com>
On Thu, Feb 16, 2017 at 12:35:32PM +0000, Shantanoo Desai wrote:
> I have developed a Multicast based Data Distribution protocol and would
> like to compare it with Batman's Multicast feature.
Cool :-)! I would love to do the same, or at least have a look at
the protocol algorithm you have developed. Is there any additional
information about it available online somewhere?
Does that protocol distribute the data to all nodes or just the
ones interested in it?
Regards, Linus
next prev parent reply other threads:[~2017-02-16 14:33 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 [this message]
2017-02-17 7:56 ` Sven Eckelmann
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=20170216143347.GC24635@otheros \
--to=linus.luessing@c0d3.blue \
--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