<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Dear Aleksi, WG,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 06 Mar 2015, at 04:17, Aleksi Suhonen <<a href="mailto:ripe-ml-2012@ssd.axu.tm" class="">ripe-ml-2012@ssd.axu.tm</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Hello,<br class=""><br class=""><blockquote type="cite" class="">On 25 Feb 2015, at 13:27, Marco d'Itri <<a href="mailto:md@Linux.IT" class="">md@Linux.IT</a>> wrote:<br class=""><blockquote type="cite" class="">Good idea. Is the up to date business logic of the database<br class="">available somewhere?<br class=""></blockquote></blockquote><br class="">On 02/25/2015 06:21 PM, Tim Bruijnzeels wrote:<br class=""><blockquote type="cite" class="">The business logic is how we typically implement RIPE policy<br class="">restrictions on the RIPE database. These restrictions are documented<br class="">in RIPE policy documents and implementation plans.<br class=""></blockquote><br class="">I think what Marco d'Itri wanted, and what I want in any case, is to see the programme code or logic statements that implement the restrictions documented in RIPE policy documents etc.<br class=""><br class="">We as a community want to verify that our wishes are implemented correctly and transparently. Some may even want to point out inaccuracies or offer corrections or performance enhancements. As long as they are within the scope of agreed policy I don't see why this could be a problem.<br class=""><br class="">The RIPE DB software is sufficiently large that we'd like a pointer to where we should start looking for said code, instead of going through the whole thing ourselves.<br class=""></div></blockquote><div><br class=""></div><div>The code for all these additional validations applied to updates can be found here:</div><div><a href="https://github.com/RIPE-NCC/whois/tree/master/whois-update/src/main/java/net/ripe/db/whois/update/handler/validator" class="">https://github.com/RIPE-NCC/whois/tree/master/whois-update/src/main/java/net/ripe/db/whois/update/handler/validator</a></div><div><br class=""></div><div>However, implementation details may not always be obvious without knowing the larger code base, and not everyone can read Java code.</div><div><br class=""></div><div>For this reason we are also working on a text document listing the existing rules per object type, plus the reasoning and references behind each rule. Doing this properly takes some time, but we are fully committed to providing transparency on these rules to everyone in an easy to understand format.</div><div><br class=""></div><div><br class=""></div><div>Kind regards,</div><div><br class=""></div><div>Tim Bruijnzeels</div><div><br class=""></div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><br class="">Yours sincerely,<br class=""><br class="">-- <br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Aleksi Suhonen<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Let bogons be bogons.<br class=""></div></blockquote></div><br class=""></div></body></html>