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: Wed, 23 Oct 2013 06:04:45 +0800 [thread overview]
Message-ID: <2255991.JK9p696vaN@diderot> (raw)
In-Reply-To: <20131022212604.GA6214@Linus-Debian>
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
On Tuesday 22 October 2013 23:26:05 Linus Lüssing wrote:
> With the current TVLV approach it is still going to be difficult
> to introduce new features / changes to batman-adv broadcast /
> coded / fragment / ... packets as the current approach only
> provides TVLVs for OGMs and unicast packets.
What kind of features are missing ? Can we please stay specific and not drift
into the "meta" future where everything and anything could be added ? What is
the feature or the features we are talking about ?
> How difficult, I'm not quite sure. Initially I thought compat
> bumps would be needed for new broadcast features for instance,
> but now I realized, that this is not the case, because bcast features
> could be signalized via OGM TVLVs and like with the mcast patches,
> could be enabled only if all nodes have that bcast-feature OGM
> TVLV.
Currently, I could not come up with a bcast feature we would want to add that
requires a compat bump. Please name it/them and state why a compat bump would
be needed. This is where the discussion can start.
> For the disadvantages of moving 'TVLVs down to the common header',
> I'm actually having trouble getting them. Maybe others could list
> them again and I try to explain which of these I'm having trouble
> understanding and why?
Again, let's start with an advantage of adding TVLVs using a practical
example. We don't want to implement TVLVs for the sake of implementing TVLVs.
Cheers,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2013-10-22 22:04 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
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 [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=2255991.JK9p696vaN@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