<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt><font size="-1"><br>
assert: the daemon name should be ntpsnmpd<br>
<br>
assert: both ipv4 and ipv6 should be implemented<br>
assert: if both exist, they should be bound at the same time<br>
<br>
assert: the port(s) should be choosable<br>
<br>
=====================================================================<br>
SNMP version / security<br>
<br>
According to RFC-5907 it is Recommended to use SNMPv3 and it's
security<br>
features, and use of previous versions of SNMP is Not
Recommended. Since<br>
NTPsec is about security and removing / not adding unnecessary
complexity,<br>
these Recommendations will be treated as Requirements, and only
SNMPv3 will<br>
be implemented.<br>
<br>
assert: security should be optional<br>
<br>
=====================================================================<br>
Dependencies: pysnmp, pysmi, python-daemon<br>
<br>
The need for pysnmp is obvious, and has already been discussed.
pysmi is by<br>
the same author, and is an MIB compiler for pysnmp.<br>
<br>
python-daemon is an implementation of PEP 3143. According to the
PEP and other<br>
info getting a daemon right is finicky, python-daemon exists to
handle that.<br>
It is currently on version 2.1.2, and listed as
"Production/Stable" dev status<br>
in the package index, so it has a low probability of existence
failure.<br>
<br>
Given the description of Proper Daemon Behavior as "fiddly", my
inexperience,<br>
and NTPsec's interest in reducing complexity where possible I
believe the<br>
addition of /another/ dependency is justified.<br>
</font></tt><br>
<pre class="moz-signature" cols="72">--
In the end; what separates a Man, from a Slave? Money? Power?
No. A Man Chooses, a Slave Obeys. -- Andrew Ryan
</pre>
</body>
</html>