Hi Ed,

>
> Whois does validate the holes attribute when creating or updating a route/route6 object, but these invalid values were added before this rule was added (in 2009 or earlier).

The attributes of the object I observed, say it was created in 2011 and
modified in 2017.

>
> Unfortunately, no cleanup was done when this rule was implemented, but in recent times we try to do this. I will also contact the maintainers of these route objects and ask them to fix the holes attribute(s).
>
> In general, if you are parsing RIPE database objects, be sure to check for invalid values.

That's what we do ... we silently drop any object containing invalid
values and do not accept them at all. This one only came to my attention
as it was just parsed while I increased log-level to debug and
live-watched the logfile.

>
> Thanks for your feedback.

It's in my own interest ;)

.... and yes ... I also give a +1 for removing the holes attribute
completely ;)



Best regards
Jens

--
Jens Ott
Geschäftsführer

Opteamax GmbH

Simrockstr. 4b
53619 Rheinbreitbach

Tel.:  +49 2224 969500
Fax:   +49 2224 97691059
Email: jo@opteamax.de

HRB: 23144, Amtsgericht Montabaur
Geschäftsführer: Jens Ott
Umsatzsteuer-ID.: DE264133989