CcNSO Policy Development Process - IDN Strings: Difference between revisions

(One intermediate revision by one other user not shown)

Line 8:

}}

The '''ccNSO Policy Development Process - (de-) selection of IDN ccTLD Strings (PDP-IDN)''' working group's goal is to report on and recommend a policy process for the "retirement" (de-selection) of [[Internationalized Domain Name|IDN strings]] associated with country code top-level domains, and to establish a policy for management of variant TLD strings in non-ASCII character sets.<ref name="ccnso">[https://ccnso.icann.org/en/workinggroups/idn-cctld-strings.htm ccNSO - PDP-IDN homepage]</ref>

The '''ccNSO Policy Development Process - (de-) selection of IDN ccTLD Strings (PDP-IDN)''' working group's goal is to report on and recommend a policy process for the "retirement" (de-selection) of [[Internationalized Domain Name|IDN strings]] associated with country code top-level domains, and to establish a policy for management of variant TLD strings in non-ASCII character sets.<ref name="ccnso">[https://ccnso.icann.org/en/workinggroups/idn-cctld-strings.htm ccNSO - PDP-IDN homepage]</ref> ccPDP4 defines the criteria, process, and procedures for (de)selecting IDN ccTLD strings to eventually replace the IDN ccTLD Fast Track Process. This PDP has three subgroups: variant management, confusing similarity review, and de-selection.<ref>[https://community.icann.org/display/ccnsowkspc/ICANN76+%7C+ccNSO+Session+Highlights ICANN76 Session Highlights]</ref>

==History==

Line 22:

Variants of TLD strings are possible within certain character sets such as Arabic or Han. The ICANN Board, in the interests of the stability of the DNS, has issued guidance regarding how and when variant strings will be accepted.<ref>[https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-07-26-en ICANN.org - Variant TLD Implementation], July 26, 1028</ref>

De-selection of IDN strings would, in theory, occur in similar circumstances as retirement of ASCII two-letter ccTLDs; either because of removal of a specific country code from the [[ISO-3166|ISO 3166-1]] list, or alterations to a country code not currently on the ISO-3166-1 list (i.e. an exceptionally reserved code such as UK).<ref name="charter" />

De-selection of IDN strings would, in theory, occur in similar circumstances as the retirement of ASCII two-letter ccTLDs; either because of the removal of a specific country code from the [[ISO-3166|ISO 3166-1]] list, or alterations to a country code not currently on the ISO-3166-1 list (i.e. an exceptionally reserved code such as UK).<ref name="charter" />

==References==

@@ Line 8: / Line 8: @@
 }}
-The '''ccNSO Policy Development Process - (de-) selection of IDN ccTLD Strings (PDP-IDN)''' working group's goal is to report on and recommend a policy process for the "retirement" (de-selection) of [[Internationalized Domain Name|IDN strings]] associated with country code top-level domains, and to establish a policy for management of variant TLD strings in non-ASCII character sets.<ref name="ccnso">[https://ccnso.icann.org/en/workinggroups/idn-cctld-strings.htm ccNSO - PDP-IDN homepage]</ref>
+The '''ccNSO Policy Development Process - (de-) selection of IDN ccTLD Strings (PDP-IDN)''' working group's goal is to report on and recommend a policy process for the "retirement" (de-selection) of [[Internationalized Domain Name|IDN strings]] associated with country code top-level domains, and to establish a policy for management of variant TLD strings in non-ASCII character sets.<ref name="ccnso">[https://ccnso.icann.org/en/workinggroups/idn-cctld-strings.htm ccNSO - PDP-IDN homepage]</ref> ccPDP4 defines the criteria, process, and procedures for (de)selecting IDN ccTLD strings to eventually replace the IDN ccTLD Fast Track Process. This PDP has three subgroups: variant management,  confusing similarity review, and de-selection.<ref>[https://community.icann.org/display/ccnsowkspc/ICANN76+%7C+ccNSO+Session+Highlights ICANN76 Session Highlights]</ref>
 ==History==
@@ Line 22: / Line 22: @@
 Variants of TLD strings are possible within certain character sets such as Arabic or Han. The ICANN Board, in the interests of the stability of the DNS, has issued guidance regarding how and when variant strings will be accepted.<ref>[https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-07-26-en ICANN.org - Variant TLD Implementation], July 26, 1028</ref>
-De-selection of IDN strings would, in theory, occur in similar circumstances as retirement of ASCII two-letter ccTLDs; either because of removal of a specific country code from the [[ISO-3166|ISO 3166-1]] list, or alterations to a country code not currently on the ISO-3166-1 list (i.e. an exceptionally reserved code such as UK).<ref name="charter" />
+De-selection of IDN strings would, in theory, occur in similar circumstances as the retirement of ASCII two-letter ccTLDs; either because of the removal of a specific country code from the [[ISO-3166|ISO 3166-1]] list, or alterations to a country code not currently on the ISO-3166-1 list (i.e. an exceptionally reserved code such as UK).<ref name="charter" />
 ==References==