linux-kernel - Re: batman-adv: design suggestions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 14 Aug 2010 19:10:57 +0200
From:	Marek Lindner <lindner_marek@...oo.de>
To:	Vasiliy Kulikov <segooon@...il.com>
Cc:	Sven Eckelmann <sven.eckelmann@....de>,
	"Greg Kroah-Hartman" <gregkh@...e.de>,
	Andrew Lunn <andrew@...n.ch>,
	Simon Wunderlich <siwu@....tu-chemnitz.de>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	Linus Lüssing <linus.luessing@....de>
Subject: Re: batman-adv: design suggestions

On Saturday 14 August 2010 18:19:15 Vasiliy Kulikov wrote:
> > 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? :)

As you could see we already made the first "registration" attempt when we wrote 
the RFC draft. Unfortunately, we neither have the academic background nor the 
lobby to push things through. But help / ideas / etc are welcome. We are still 
very interested in seeing this happen.

We are constantly tweaking / improving the protocol which should not hinder 
such a standardization. 

Cheers,
Marek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/