<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<span>
</span><br>
<blockquote style="border: 0px none;"
cite="mid:mailman.5.1453291202.43884.kea-dev@lists.isc.org" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true"
href="mailto:kea-dev-request@lists.isc.org" style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">kea-dev-request@lists.isc.org</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">20
Jan 2016 13:00</span></font></div> </div></div>
<div style="color: rgb(136, 136, 136); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><div>Send
kea-dev mailing list submissions to<br> <a class="moz-txt-link-abbreviated" href="mailto:kea-dev@lists.isc.org">kea-dev@lists.isc.org</a><br><br>To
subscribe or unsubscribe via the World Wide Web, visit<br>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/kea-dev">https://lists.isc.org/mailman/listinfo/kea-dev</a><br>or, via email, send a
message with subject or body 'help' to<br> <a class="moz-txt-link-abbreviated" href="mailto:kea-dev-request@lists.isc.org">kea-dev-request@lists.isc.org</a><br><br>You
can reach the person managing the list at<br>
<a class="moz-txt-link-abbreviated" href="mailto:kea-dev-owner@lists.isc.org">kea-dev-owner@lists.isc.org</a><br><br>When replying, please edit your
Subject line so it is more specific<br>than "Re: Contents of kea-dev
digest..."<br><br><br>Today's Topics:<br><br> 1. Extending client
classification in Kea 1.1 -<br> requirements/design (Tomek
Mrugalski)<br><br><br>----------------------------------------------------------------------<br><br>Message:
1<br>Date: Tue, 19 Jan 2016 20:36:15 +0100<br>From: Tomek Mrugalski
<a class="moz-txt-link-rfc2396E" href="mailto:tomasz@isc.org"><tomasz@isc.org></a><br>To: <a class="moz-txt-link-rfc2396E" href="mailto:kea-dev@lists.isc.org">"kea-dev@lists.isc.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:kea-dev@lists.isc.org"><kea-dev@lists.isc.org></a><br>Subject: [kea-dev] Extending client
classification in Kea 1.1 -<br> requirements/design<br>Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:569E902F.80803@isc.org"><569E902F.80803@isc.org></a><br>Content-Type: text/plain;
charset=utf-8<br><br>Hello everyone,<br><br>We have implemented a
somewhat basic client classification in Kea 1.0.<br>It is working for
some scenarios, but currently lacks fancier features.<br>We do have a
plan to extend it in Kea 1.1. I have updated the<br>requirements [1] and
design [2] documents. It would be great if you<br>could read and
comment on them.<br><br>The existing stuff from Kea 1.0 is referred to
as phase 1. Plans for Kea<br>1.1 are referred to as phase 2. Phase 3 are
things that we'd like to get<br>one day, but decided not to do them in
the Kea 1.1 timeframe.<br><br>In particular, there are couple ideas in
the Open Questions section that<br>require comments from developers and
users. I list the questions here,<br>but please do read the [1] document
as it provides more background reasons:<br><br>Q1: We do have boolean
(and, or, not) operators designed and planned for<br>1.1. Do we also
want arithmetic comparison (>, <, >=, <=) operators?<br><br>Q2:
Do we want find(string, what) operator?<br><br>Q3: Do we want
len(string) operator?<br><br>Q4: Do we want option[123].len specifier?<br><br>Q5:
Do we want to have an ability to specify that if packet is matched<br>to
a class, the packet is immediately dropped?<br><br>The links are:<br>1.
<a class="moz-txt-link-freetext" href="http://kea.isc.org/wiki/ClientClassificationRequirements">http://kea.isc.org/wiki/ClientClassificationRequirements</a><br>2.
<a class="moz-txt-link-freetext" href="http://kea.isc.org/wiki/ClientClassificationDesign">http://kea.isc.org/wiki/ClientClassificationDesign</a><br><br>We would like
to get going with the implementation, so please send your<br>comments no
later than 2016-01-26 (the next Wednesday).<br><br>Thanks,<br>Tomek<br></div></div>
</blockquote>
<br>
I missed the feedback deadline but FWIW I think creating too complex a
classification syntax risks leading you into the maintenance rathole
that you were trying to avoid when writing KEA: you are in danger of
recreating a high level language (in the configuration).<br>
<br>
I humbly suggest that your time might be more productively spent on
providing a set of (tested) libraries and example hooks that would allow
others to quickly develop specific hooks directly in c++ that can be
loaded into the DHCP server. Packet and options parsing, packet and
options construction for outbound packets, config parsing, and database
lookups to file/mysql etc., are all reasonably painful operations and
could benefit for a standard and well-documented API.<br>
<br>
regards,<br>
<blockquote style="border: 0px none;"
cite="mid:mailman.5.1453291202.43884.kea-dev@lists.isc.org" type="cite">
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<div><br><br>------------------------------<br><br>_______________________________________________<br>kea-dev
mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:kea-dev@lists.isc.org">kea-dev@lists.isc.org</a><br><a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/kea-dev">https://lists.isc.org/mailman/listinfo/kea-dev</a><br><br>End
of kea-dev Digest, Vol 22, Issue 7<br>**************************************<br></div>
</div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div>regards,<br>
RayH<span style="text-decoration: underline;"><br>
</span><a
href="https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach"><span
style="color: rgb(51, 102, 153);"></span></a></div>
</div>
</body></html>