Should a list of IDN ccTLD strings be mandated?
At the initial stage of this project, it is important to have the list of IDN ccTLD strings mandated. Not having a mandated list can lead to important process/concept related problems/issues. One way to do it is to apply the same methodology applied for the ASCII case, in which the ccTLDs are mandated based on the ISO 3166 list, but as ISO has declined such role, the list of IDN ccTLD strings can be mandated by another body, which would mandate ccTLD string in the certain characters to represent each territory. On the other hand, the simplest way not the easiest though, is to have ccTLDs/ISO 3166 list automatically become the mandated list of IDN ccTLD – under the clear monitorisation of an authoritative body. If this new project requires to be implemented under a certain policy, then it is mandatory that ccTLD community is consulted for this purpose. The input of the ccTLD community should be based on the inputs of the users of those communities and a Needs Assessment should be carrie
Related Questions
- What does it mean for the IDN ccTLD manager that domains under synchronized IDN ccTLDs must resolve to the same address or value?
- Does dbx have a list of RS-232 strings for controlling the ZonePRO products via a 3rd party controller?
- Can an IDN ccTLD change from being synchronized to not being synchronized?
