<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="+1"><tt>Dear Job and Tore<br>
<br>
Thanks for pointing this out and for the patch. It seems there
was some misinterpretation of the RFC when this feature was
implemented. The documentation states it must be an address
prefix. But the implementation accepted either an address or an
address prefix.<br>
<br>
Thanks for the patch Job. The developers will check it to make
sure it now accepts only an address and fails on an address
prefix...which is what the RFC states. Then we will update the
documentation to reflect this.<br>
<br>
regards<br>
Denis Walker<br>
Business Analyst<br>
RIPE NCC Database Team<br>
<br>
</tt></font>
<div class="moz-cite-prefix">On 15/03/2014 21:32, Job Snijders
wrote:<br>
</div>
<blockquote cite="mid:20140315203206.GY10117@Eleanor.local"
type="cite">
<pre wrap="">On Sat, Mar 15, 2014 at 03:44:16PM +0100, Job Snijders wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">The documentation unequivocally states the value of the "pingable"
attribute in route[6] objects must include a prefix length:
</pre>
</blockquote>
<pre wrap="">
<snip>
Nice catch Tore!
</pre>
</blockquote>
<pre wrap="">
When this commit is merged the documentation will be aligned with
expected behaviour.
<a class="moz-txt-link-freetext" href="https://github.com/RIPE-NCC/whois/pull/189">https://github.com/RIPE-NCC/whois/pull/189</a>
Have a good weekend, and keep hunting for bugs! :-)
Job
</pre>
</blockquote>
<br>
</body>
</html>