Hi Laurent, "...country attribute at inetnum level despite RIPE NCC has spent the last 20 years telling people they cannot rely on that attribute for IP location)." This is the confusion - It is only the country values in the extended delegated stats file, consistent, taken from the 'country' attribute in the organisation object (RIPE NCC managed value) which should not be used for IP location. While the 'country' attribute in the inetnum object was left available/optional for LIR to indicate a geolocation.
The country code value, where the resource holder is legally based, is also used by RIPE NCC to make up the regID and RIPE NCC used the regID to build up ‘netname’ attribute in all inet(6)num objects for PA allocations issued to LIRs. Therefore, this is a possible case of conflicting value - different country code in the netname attribute and in the country attribute in a same inetnum. I share the idea that there should be a single attribute (not using a country code value) officially supported for geolocation purposes. Thanks Best regards Eric Delmas
-- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
