Yes I know allocations and assignments can be announced from multiple countries, but a member has this option to set the country code for allocation and assignments based on their needs. If I can set my allocation's country code in RIPE DB why I should not be able to have the same value in delegation file for the same allocation?
Having different values for country code in DB and delegation file for exact same allocation will make more confusion and can break networks, Currently country codes in the RIPE Database are quite consistent with the extended delegated file, I wish someone from RIPE NCC can run a test and confirm this.
A workable solution to me is to let we have this consistency between DB and delegation file, and I don't see an actual need to break it.
Regards,
Arash Naderpour
Arash,
Arash Naderpour wrote:
> What you name it as "meaningless values" are not meaningless to
> the organizations that they are using it.
How do we know that all, or even most, users of the data infer the same meanings? Has the RIPE NCC or anyone else ever measured what people understand this value to mean and the operational purposes to which it is put?
> When you request a new allocation from NCC you will be asked to
> "specify the country which the allocation will be announced", and
> based on your selection the country code will be set for both the
> inet(6)numns and allocation entry in the delegation file. This is the
> way that the country code is added in first place in delegation file.
This was not always the case. Furthermore, allocations are not necessarily announced as single aggregate or from a single country. It is entirely possible for an allocation to be announced from multiple countries, or to be split into smaller blocks that are announced from different countries. The stats file is just about good enough to give some idea of the distribution of Internet Number Resources in different countries in a statistically useful way. But using the country code information in it to make operational decisions seems to be placing weight on both the meaning and accuracy of the data that is probably not justifiable.
Kind regards,
Leo Vegoda