From: Vasiliy Kulikov <segooon@gmail.com>
To: Marek Lindner <lindner_marek@yahoo.de>
Cc: "Sven Eckelmann" <sven.eckelmann@gmx.de>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
"Andrew Lunn" <andrew@lunn.ch>,
"Simon Wunderlich" <siwu@hrz.tu-chemnitz.de>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
"Linus Lüssing" <linus.luessing@web.de>
Subject: Re: batman-adv: design suggestions
Date: Sat, 14 Aug 2010 20:19:15 +0400 [thread overview]
Message-ID: <20100814161915.GB3258@albatros> (raw)
In-Reply-To: <201008141650.57375.lindner_marek@yahoo.de>
On Sat, Aug 14, 2010 at 16:50 +0200, Marek Lindner wrote:
> On Thursday 12 August 2010 14:48:13 Vasiliy Kulikov wrote:
> > Is there any (un)official documentation/RFC/whatever of batman-adv
> > protocol? I found only expired RFC of batman that is using UDP at
> > www.open-mesh.org.
>
> Yes, there is an unofficial one:
> http://gitorious.org/batman-adv-doc
Thank you!
> Note: This document is neither complete nor up to date. Writing proper
> documentation for the routing protocol is on our long ToDo list.
Do you plan to register it as RFC/IEEE/whatever when linux batman-adv
implementation is stabilized? Or you plan to improve it somehow? :)
>
> The UDP version is very similar to the kernel module since we used the user
> space implementation to verify the concept.
>
>
> Cheers,
> Marek
next prev parent reply other threads:[~2010-08-14 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 20:34 batman-adv: design suggestions Vasiliy Kulikov
2010-08-09 20:53 ` Sven Eckelmann
2010-08-12 12:48 ` Vasiliy Kulikov
2010-08-14 14:50 ` Marek Lindner
2010-08-14 16:19 ` Vasiliy Kulikov [this message]
2010-08-14 17:10 ` Marek Lindner
2010-08-13 18:18 ` Vasiliy Kulikov
2010-08-13 23:25 ` Sven Eckelmann
2010-08-14 14:59 ` Marek Lindner
2010-08-14 16:13 ` Vasiliy Kulikov
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=20100814161915.GB3258@albatros \
--to=segooon@gmail.com \
--cc=andrew@lunn.ch \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=lindner_marek@yahoo.de \
--cc=linus.luessing@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=sven.eckelmann@gmx.de \
/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