EPDP on Internationalized Domain Names: Difference between revisions

Line 24:

# IDN Implementation Guidelines.<ref>[https://75.schedule.icann.org/meetings/LNAKr9E4yGB5kw6mZ EPDP-IDN Working Group Session 1, ICANN75]</ref>

In ~~September 2022~~, the WG presented its plan to break the initial report into "chunks." It has several reasons for doing so including:

In ICANN 75 Session 1, the WG presented its plan to break the initial report into "chunks." It has several reasons for doing so including:

# its charter deliberation is behind schedule due to the breadth and complexity of issues related to IDN variants,

# more data need to be collected from registries, registrars, and RSPs about second-level variant management,

# the impact on the New gTLD Application process and SubPro recommendation implementation, and

# “Second-level” charter questions following gTLD delegation that new gTLD applicants do not need to address.<ref>[https://75.schedule.icann.org/meetings/LNAKr9E4yGB5kw6mZ EPDP-IDN Working Group Session 1, ICANN75]</ref>

In ICANN 75 Session 2, the WG presented its findings from a survey among Chinese and Arabic ROs, of which 20/26 and 2/9 responded, respectively. In terms of interest in Activating Variants, 12 Chinese ROs and 2 Arabic ROs responded, "Yes.” Potential factors affecting their future decisions included market condition, business potential, registrar interest, variant domain use and access, the New Applicant Guidebook, IDN policies, contractual terms, cost/fees, the application, transactions, management/hosting, variant domain management, complexity, behavior, resolution system design, capacity expansion, specific gTLD launches, and timing.<ref>[https://75.schedule.icann.org/meetings/WwNt9pJZQvHwZnZmA EPDP-IDN WG Session 2, ICANN 75]</ref>

==References==

[[Category:EPDPs]]

@@ Line 24: / Line 24: @@
 # IDN Implementation Guidelines.<ref>[https://75.schedule.icann.org/meetings/LNAKr9E4yGB5kw6mZ EPDP-IDN Working Group Session 1, ICANN75]</ref>
-In September 2022, the WG presented its plan to break the initial report into "chunks." It has several reasons for doing so including:
+In ICANN 75 Session 1, the WG presented its plan to break the initial report into "chunks." It has several reasons for doing so including:
 # its charter deliberation is behind schedule due to the breadth and complexity of issues related to IDN variants,
 # more data need to be collected from registries, registrars, and RSPs about second-level variant management,
 # the impact on the New gTLD Application process and SubPro recommendation implementation, and
 # “Second-level” charter questions following gTLD delegation that new gTLD applicants do not need to address.<ref>[https://75.schedule.icann.org/meetings/LNAKr9E4yGB5kw6mZ EPDP-IDN Working Group Session 1, ICANN75]</ref>
+In ICANN 75 Session 2, the WG presented its findings from a survey among Chinese and Arabic ROs, of which 20/26 and 2/9 responded, respectively. In terms of interest in Activating Variants, 12 Chinese ROs and 2 Arabic ROs responded, "Yes.” Potential factors affecting their future decisions included market condition, business potential, registrar interest, variant domain use and access, the New Applicant Guidebook, IDN policies, contractual terms, cost/fees, the application, transactions, management/hosting, variant domain management, complexity, behavior, resolution system design, capacity expansion, specific gTLD launches, and timing.<ref>[https://75.schedule.icann.org/meetings/WwNt9pJZQvHwZnZmA EPDP-IDN WG Session 2, ICANN 75]</ref>
 ==References==
 [[Category:EPDPs]]