-
Notifications
You must be signed in to change notification settings - Fork 0
rir-ip / iso3166 and EU #13
-
Per ISO 3166, 'EU' is not a defined country code as the rir-ip breakout would suggest:
{
"country": "European Union",
"country-code": "EU",
"delegation-status": [
"allocated",
"assigned"
],
"mode": "aggregated",
"subnets": {
"ipv4": [
"138.199.64.0/20",
"139.191.0.0/16",
"144.44.0.0/16",
"145.218.0.0/16",
"151.175.0.0/16",
"158.67.0.0/16",
"192.84.203.0/24",
"192.108.27.0/24",
"192.108.28.0/23",
"192.108.30.0/24"
],
"ipv6": []
}
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 3 comments 2 replies
-
Since it's in a reserved status in https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#EU I don't see a problem here.
Beta Was this translation helpful? Give feedback.
All reactions
-
In general I understand and appreciate your statement.
I ran into an issue while updating some legacy code that indexes on country-code not the alpha-2 field.
It's easy enough to inject arbitrary values for the missing fields, and still call out the data exceptions.
Unfortunately, without standard values I'll need exceptions for other IP location tools as well.
Beta Was this translation helpful? Give feedback.
All reactions
-
Are you parsing the list of subdirectory entries in the country directory? If so, why don't you just omit EU?
Beta Was this translation helpful? Give feedback.
All reactions
-
Considered that too, but the code base is attempting to sequentially map the entire IP range. Given the ranges appear unallocated the method I use at this time is of little consequence. It's just a data anomaly.
Beta Was this translation helpful? Give feedback.
All reactions
-
The EU's gone for good ;-)
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1