public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <ordex@autistici.org>
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.] Dynamic OGM interval
Date: Tue, 29 Jan 2013 10:13:32 +0100	[thread overview]
Message-ID: <20130129091332.GA15011@ritirata.org> (raw)
In-Reply-To: <51079137.7040205@hundeboll.net>

[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]

On Tue, Jan 29, 2013 at 10:07:03 +0100, Martin Hundebøll wrote:
> On 2013-01-29 09:54, ajeet singh wrote:
> > Is there any plane to support dynamic OGM interval selection in future?
> 
> No, not at the moment. But the design of the next-generation protocol is 
> on the sketch-board, and I guess that the concept of "reactive" OGMs is 
> part of the ideas.

Yeah, the next-generation protocol (namely B.A.T.M.A.N. V) is going to
change the way information are spread over the network. In particular we planned
to split the link quality detection from the TQ spreading mechanism.
You can read more at [1], [2] and [3].

But still we have clearly identify the way we
want the "reactive" OGM to behave..and other things...

So, of course, feel free to contribute! :-)

Cheers,

[1] http://www.open-mesh.org/projects/batman-adv/wiki/ELP
[2] http://www.open-mesh.org/projects/batman-adv/wiki/OGM
[3] http://www.open-mesh.org/projects/batman-adv/wiki/Ogm-v2


-- 
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-01-29  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29  8:54 [B.A.T.M.A.N.] Dynamic OGM interval ajeet singh
2013-01-29  9:07 ` Martin Hundebøll
2013-01-29  9:13   ` Antonio Quartulli [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=20130129091332.GA15011@ritirata.org \
    --to=ordex@autistici.org \
    --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