From: Marek Lindner <mareklindner@neomailbox.ch>
To: 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.] A few questions on TVLV
Date: Sun, 20 Oct 2013 18:26:41 +0800 [thread overview]
Message-ID: <1989798.ZHJlJXvcrz@diderot> (raw)
In-Reply-To: <20131020082506.GC13550@Linus-Debian>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Sunday 20 October 2013 10:25:07 Linus Lüssing wrote:
> I think I had posted some thoughts on the TVLV feature on the IRC
> channel before with some suggestions for changes (e.g. moving the
> TVLV feature from the individual packet types down to the common
> batman header). And had tried to come up with examples for
> features where TVLVs for batman broadcast packets could be useful
> - which might have been potential, but not the most convincing,
> not the most awesome features.
>
> So now I have a feature which I would like to have / would like to
> work on in the future [0], and I would like to know:
Before we discuss how we get TVLVs 'down to the common batman header' we
should talk about why that would be useful. What are the advantages and
disadvantages ? Adding tvlvs everywhere for the mere sake of having them
around isn't good enough as they increase code complexity, network traffic
overhead and encapsulation speed penalties.
Cheers,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-10-20 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 8:25 [B.A.T.M.A.N.] A few questions on TVLV Linus Lüssing
2013-10-20 10:26 ` Marek Lindner [this message]
2013-10-22 21:26 ` Linus Lüssing
2013-10-22 21:47 ` Linus Lüssing
2013-10-22 22:16 ` Marek Lindner
2013-10-22 22:04 ` 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=1989798.ZHJlJXvcrz@diderot \
--to=mareklindner@neomailbox.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.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