<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hola Erick,<br>
Me parece super buena la respuesta recibida de ISC..., solo me
queda decirte que en caso de que quieras/puedas compartir tu
experiencia despues seria genial!!. Yo he usado el ISC DHCP mas no
conocia el Kea..<br>
<br>
Saludos y mucha suerte con la opcion que elijas!!,<br>
<br>
Alejandro,<br>
<br>
El 9/23/2014 a las #4, Erick Lobo Marín escribió:<br>
</div>
<blockquote
cite="mid:CAL3WifL4Oo-CmYbqW7j0LVEzdT_n2OPpiow4S35+tsXp6my45w@mail.gmail.com"
type="cite">
<div dir="ltr">Copio respuesta de ISC:
<div><br>
</div>
<div>
<div>2014-09-23 10:24 GMT-06:00 Tomek Mrugalski <<a
moz-do-not-send="true" href="mailto:tomasz@isc.org">tomasz@isc.org</a>>:</div>
<div>On 23.09.2014 16:37, Erick Lobo Marín wrote:</div>
<div>> Hi, What alternative recommended for select DHCP in
a Network Enterprise:</div>
<div>></div>
<div>> a) The roadmap ISC DHCP 4.3 .x</div>
<div>> b) The roadmap kea DHCP, currently in version 0.9 ?</div>
<div>Those two DHCP solutions are in radically different
cycles.</div>
<div>ISC DHCP is an old, well proven software with lots of
features and</div>
<div>history behind it. Its development is slower than Kea.
ISC provides paid</div>
<div>support for ISC DHCP, if you need it. ISC DHCP supports
failover for</div>
<div>DHCPv4, while Kea does not.</div>
<div><br>
</div>
<div>Kea is a new solution that officially haven't reached
1.0. ISC does not</div>
<div>offer support contract for it yet. It is in many cases
much faster than</div>
<div>ISC DHCP. It has fewer features, but has some features
that are not</div>
<div>present in ISC DHCP (e.g. hooks or lease storage in MySQL
or Postgres).</div>
<div>As this is a relatively young software, it is sometimes a
bit rough on</div>
<div>edges. On the other hand, it is being very actively
developed.</div>
<div>Significant new features are added every release.</div>
<div><br>
</div>
<div>If you report a bug, it is more likely that Kea will be
able to deliver</div>
<div>a fix faster. (That obviously depends on the severity of
the bug. I'm</div>
<div>thinking about a typical bug, not a security issue).</div>
<div><br>
</div>
<div>So if you consider yourself an early adopter, you may
want to take a</div>
<div>look at Kea. If you want to know current state of Kea
capabilities, the</div>
<div>following 2 links could be useful:</div>
<div><a moz-do-not-send="true"
href="http://kea.isc.org/wiki/KeaUpdate2">http://kea.isc.org/wiki/KeaUpdate2</a>
- May 2014</div>
<div><a moz-do-not-send="true"
href="http://kea.isc.org/wiki/KeaUpdate3">http://kea.isc.org/wiki/KeaUpdate3</a>
- Set 2014</div>
<div><br>
</div>
<div>So it's really up to you and your specific preferences.
Do you need to</div>
<div>keep your leases in MySQL? Use Kea. Do you need to do
fancy client</div>
<div>management and access control? ISC DHCP will probably be
better. Do you</div>
<div>plan to extend your DHCP server with your own logic,
consult with</div>
<div>external database, log in some unusual way? Then perhaps
hooks in Kea</div>
<div>are more appealing for you? Excited about new features
being added</div>
<div>frequently? Pick Kea. Need stability with minimal
changes? Pick ISC</div>
<div>DHCP, preferably ESV. Do you need host reservation? If
yes, what is your</div>
<div>deployment timeframe? ISC DHCP supports it for a decade
or more. Kea</div>
<div>will support it in upcoming 0.9.1, which is couple months
away.</div>
<div><br>
</div>
<div>Need high performance? How big is your enterprise? How
many leases/sec</div>
<div>or how many subnets you expect the server to be handling?
Do you need</div>
<div>full failover? Maybe MySQL or Postgres high availability
solutions will</div>
<div>be enough for you?</div>
<div><br>
</div>
<div>These are all questions you will need to answer yourself.
My</div>
<div>recommendation is that you should get both, test them and
see which one</div>
<div>works better for you.</div>
<div><br>
</div>
<div>Hope that helps,</div>
<div>Tomek</div>
<div><br>
</div>
<div>2014-09-23 14:29 GMT-06:00 Tomek Mrugalski <<a
moz-do-not-send="true" href="mailto:tomasz@isc.org">tomasz@isc.org</a>>:</div>
<div>On 23/09/14 21:45, Erick Lobo Marín wrote:</div>
<div>> Hi Tomek, Very complete your response. A doubt:</div>
<div>> What is the extended support version (ESV) release?</div>
<div>See <a moz-do-not-send="true"
href="http://www.isc.org/downloads/software-support-policy/">http://www.isc.org/downloads/software-support-policy/</a></div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div dir="ltr">Atentamente,
<div>Erick Lobo</div>
<div>Costa Rica</div>
<div><br>
</div>
<div>lgD</div>
</div>
</div>
<br>
<div class="gmail_quote">El 22 de septiembre de 2014, 14:25,
Erick Lobo Marín <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:erick.lobo@cgr.go.cr" target="_blank">erick.lobo@cgr.go.cr</a>></span>
escribió:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">
<div>Hola,</div>
<div><br>
</div>
<div>Conocen alguna implementación "Kea DHCP versión
0.9 (también llamado BIND 10) "?</div>
<div><br>
</div>
<div>Lo han podido comparar con la versión más
reciente del "ISC DHCP"?</div>
<div><br>
</div>
<div>Alguna experiencia, al respecto?</div>
<div><br>
</div>
<div>Muchas gracias,</div>
<div><br>
</div>
<div>Erick Lobo</div>
<div>Costa Rica</div>
<div>lgD</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
LACTF mailing list
<a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a>
<a class="moz-txt-link-freetext" href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a>
Cancelar suscripcion: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a></pre>
</blockquote>
<br>
</body>
</html>