Dear Job and Tore

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.

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.

regards
Denis Walker
Business Analyst
RIPE NCC Database Team
On 15/03/2014 21:32, Job Snijders wrote:
On Sat, Mar 15, 2014 at 03:44:16PM +0100, Job Snijders wrote:


The documentation unequivocally states the value of the "pingable"
attribute in route[6] objects must include a prefix length:

<snip>

Nice catch Tore!

When this commit is merged the documentation will be aligned with
expected behaviour.
    
    https://github.com/RIPE-NCC/whois/pull/189

Have a good weekend, and keep hunting for bugs! :-)

Job