"country": what to for "strange" locations?

Hello... I know there's "EU" for europe, but what to use for: - anycast services without any specific location - blackholes - ... For example, 193.0.14.0/23** (k.root-servers.net) uses "country: NL". Documentation says: "There are no rules defined for this attribute." Is there a best practice? If not, is there a chance to get "ZZ" approved for "unspecified" as ISO 3166-1 specifies "ZZ" (and some more) for "/User-assigned code elements"... Best regards, Christian /

Christian, On 2010-01-30 05:01, Christian 'wiwi' Wittenhorst wrote:
I know there's "EU" for europe, but what to use for: - anycast services without any specific location - blackholes - ...
For example, 193.0.14.0/23** (k.root-servers.net) uses "country: NL". Documentation says: "There are no rules defined for this attribute."
Is there a best practice? If not, is there a chance to get "ZZ" approved for "unspecified" as ISO 3166-1 specifies "ZZ" (and some more) for "/User-assigned code elements"...
You have stumbled upon the reason this attribute should be OPTIONAL. However, Daniel Karrenberg finds it extremely useful for some sort of research, apparently, so it is marked MANDATORY. As you have guessed, there are no good answers to your problem. One possibility is to use the fact that it is MULTIPLE and list multiple countries - so perhaps listing the country code of each of your routers. Or you can just put something in the comments. If you want ZZ, you can bring it up on the db-wg. It was discussed a few years ago, but maybe we can convince them this time? -- Shane
participants (2)
-
Christian 'wiwi' Wittenhorst
-
Shane Kerr