> - RIPE Database is set up to contain hierarchical data already. With this > proposal, we would take some of this data outside the database in a manner > that does not guarantee consistency with the database itself. For example, > 192.168/16 specifies a geofeed file that has different prefixes in it than > the children of said inetnum (or cover a range that is not even listed in > the RIPE Database).
from the i-d When using data from a geofeed file, one MUST ignore data outside of the inetnum: object's inetnum: attribute's address range. please read the draft randy
