From: Antonio Quartulli <antonio@meshcoding.com>
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.] Alfred batadv-vis json conformance
Date: Wed, 2 Oct 2013 18:01:06 +0200 [thread overview]
Message-ID: <20131002160106.GA1939@neomailbox.net> (raw)
In-Reply-To: <20131002130548.GA24077@pandem0nium>
[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]
On Wed, Oct 02, 2013 at 03:05:48PM +0200, Simon Wunderlich wrote:
> > I'm also wondering if label and gateway could have more meaningful
> > names? TQ and host? Also, is TT the best?
>
> Hm, that is a good question. We also have the batman v with new metrics
> coming up, I'm not sure how to handle these (maybe Antonio has some
> idea?). It is not the TQ-value in the label after all, but some kind of
> ETX-converted value (255/TQ if i remember correctly).
I think the ETX stuff comes from OLSR (but I don't know the details).
I agree with Simon that we should find a generic name (e.g. metric ?) but I am
not sure we can represent this value in a "algorithm-generic" fashion (and maybe
we don't want to).
>
> Maybe we can change the names to:
> * for neighbors: router->nexthop
> * TT: "gateway" -> "client", "router" -> "node", maybe also change TT to clients?
TT is specific to the mechanism we use to announce clients.
Moving to the generic "clients" could also be ok.
> >
> > I would like suggestions and comments from others with more experience
> > with json. Is the basic structure O.K. Are there better names to use?
> >
> > There is also the issue of can we change the format of the current
> > output. Is it considered an ABI? Should I add a third format string
> > which can be passed with -f to produce true json, and leave the old
> > format as is, for backward compatibility?
>
> As explained above, I'd like to keep the old format, so a third format
> string should be used. It would be nice (if possible) to consider BATMAN V
> at this point too to avoid adding many more formats in the future, but
> generally I'm okay with adding new formats.
>
I have to think about what batman v may require. But I don't see snything
special right now.
Cheers,
--
Antonio Quartulli
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-02 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 20:26 [B.A.T.M.A.N.] Alfred batadv-vis json conformance Andrew Lunn
2013-10-02 13:05 ` Simon Wunderlich
2013-10-02 13:36 ` Andrew Lunn
2013-10-06 8:35 ` Nicolás Echániz
2013-10-07 9:00 ` Andrew Lunn
2013-10-02 16:01 ` Antonio Quartulli [this message]
2013-10-03 6:09 ` Martin Hundebøll
2013-10-03 8:11 ` Andrew Lunn
2013-10-03 8:22 ` Antonio Quartulli
2013-10-03 8:53 ` Andrew Lunn
2013-10-03 9:00 ` Antonio Quartulli
2013-10-03 9:05 ` Andrew Lunn
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=20131002160106.GA1939@neomailbox.net \
--to=antonio@meshcoding.com \
--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