public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] List policy for none subscribers
Date: Thu, 27 Aug 2009 18:05:38 +0800	[thread overview]
Message-ID: <200908271805.39186.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20090826180810.GF16067@lunn.ch>

On Thursday 27 August 2009 02:08:10 Andrew Lunn wrote:
> How many of these goals can be reached without changing the packet
> format? I've implemented regenerating lost OGMs without changing the
> protocol to a degree it needs to bump the version number. Does
> removing the averaging of TQ from remote neighbors change the message
> format?
>
> My question would be, does not changing the message format so that the
> version number can stay the same impose too high a penalty in terms of
> design restrictions?

Correct me if I'm mistaken but I thought you added the originator interval ?!

In the past we did not only increase the version number when the packet format 
changed. We use that number to distinguish different ways of processing routing 
information. A packet format modification is the most obvious change but not 
the only one. If I receive a packet and interprete it completely different than 
the neighbor giving that packet to me the chance of creating routing loops is 
high. Therefore any major routing protocol change might require the version 
field to be updated.

Regards,
Marek

  reply	other threads:[~2009-08-27 10:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26  6:41 [B.A.T.M.A.N.] List policy for none subscribers Andrew Lunn
2009-08-26  7:54 ` Marek Lindner
2009-08-26  8:27   ` Andrew Lunn
2009-08-26  8:01 ` Sven Eckelmann
2009-08-26  8:51   ` Marek Lindner
2009-08-26 10:47     ` [B.A.T.M.A.N.] Breaking long lines Andrew Lunn
2009-08-26 10:52     ` [B.A.T.M.A.N.] New name for batman-adv? Andrew Lunn
2009-08-27  9:58       ` Marek Lindner
2009-08-27 19:44         ` Andrew Lunn
2009-08-28  1:57           ` Outback Dingo
2009-08-28  3:08             ` Andrew de Andrade
2009-08-28  6:42             ` Antoine van Gelder
2009-10-09 18:57         ` Linus Lüssing
2009-08-26 11:01     ` [B.A.T.M.A.N.] Configuration interface Andrew Lunn
2009-08-27 13:57     ` [B.A.T.M.A.N.] List policy for none subscribers Bernd Petrovitsch
2009-08-26  9:19   ` elektra
2009-08-26 10:41     ` Andrew Lunn
2009-08-26 18:08     ` Andrew Lunn
2009-08-27 10:05       ` Marek Lindner [this message]
2009-08-27 11:10       ` elektra
2009-08-27 14:17         ` 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=200908271805.39186.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.net \
    /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