<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div>Hi Jake,</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">This blog post says Kea is working on a secure remote management client.<br class=""><br class=""><a href="https://www.isc.org/blogs/isc-receives-mozilla-moss-award/" class="">https://www.isc.org/blogs/isc-receives-mozilla-moss-award/</a><br class=""></div></div></blockquote><div><br class=""></div>We are working on creating a remote management capability, including both a REST API on the server, and a client that implements that API. We need both, obviously, in order to prove out the API and test it on an on-going basis. We also figure that the client would be a good building block for provisioning applications.</div><div><br class=""></div><div>All the work funded by the MOSS award will be open source, including the remote client. </div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="">I have a fledgling project I am attempting to get off the ground that will<br class="">provide a dynamic web based GUI that I intend to use for managing Kea, as<br class="">well as DNS. But I do not think I can compete with you guys if you are<br class="">thinking about doing the same thing.<br class=""></div></div></blockquote><div><br class=""></div>You don’t mention whether you are planning an open source GUI or a commercial project. I don’t think you can expect exclusivity in any case. Our ISC DHCP software is the basis for at least a half dozen commercial products, and several open source tools. Kea already has one commercial GUI that I know of, from Men and Mice (<a href="https://www.menandmice.com/products/dhcp-management/" class="">https://www.menandmice.com/products/dhcp-management/</a>).</div><div><br class=""></div><div>We would like to develop some sort of commercial tools for Kea, because we need a revenue stream to support the core Kea project. In the past 2 years, besides the MOSS award we just got, we have had zero financial support for Kea. As you can tell from this list, there are several developers who work on this full-time, so obviously, we need to get something to pay them with. So, I won’t promise we won’t develop a GUI, but again, as I already mentioned, there should be room for multiple offerings.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="">I am very excited about the future of Kea and have been watching from afar<br class="">for some time now, and I would very much like to avoid duplicating effort<br class="">with the dev team.</div></div></blockquote><blockquote type="cite" class=""><div class=""><div class=""><br class="">Could someone please tell me the plans for this remote client and what it<br class="">might look like?</div></div></blockquote><div><br class=""></div>If you are looking at writing a management application for Kea, would you please look at the requirements for the API and client, and see if you can help flesh them out? (<a href="http://kea.isc.org/wiki/ControlAPICliDesign" class="">http://kea.isc.org/wiki/ControlAPICliDesign</a>)</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">- The Godfather<br class=""></div></div></blockquote><br class=""></div><div class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Victoria Risk</div><div class="">Internet Systems Consortium</div><div class=""><a href="mailto:vicky@isc.org" class="">vicky@isc.org</a></div><div class=""><br class=""></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>