AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Review Implementation Plan Development
Page History
...
Solutions are not always technical
| Wiki Markup |
|---|
Whilst the ICANN by its very nature is a type of multi stakeholder technical coordination body, it tends to seek comments and rely on comments from the technical community. The ALAC in a 2010 Statement is on record to say that not every problem has a technical solution and that ICANN should not deter from making a policy decision even when technical solutions do not exist\[[1]\|#_ftn1\]. |
An illustration to from a previous statement is as follows\[[2]\|#_ftn2\]:\- |
The Chinese SC-TC problem is a classic case. During the early days of IDN, it was proposed that SC-TC be handle within the IDN protocol. There was a long debate among the IETF Working Group participants and a strong push from the Chinese technical community.
...
ALAC would like to encourage ICANN to prioritize its efforts and exert its influence to best promoting Universal Acceptance and thanks the JIG for the initial report.
...
| Wiki Markup |
|---|
\[[1]\|#_ftnref1\] [https://community.icann.org/display/alacidnpolicy/ALAC+Statement+IDN+Issues|../../../../../../../../../../display/alacidnpolicy/ALAC+Statement+IDN+Issues] |
| Wiki Markup |
|---|
\[[2]\|#_ftnref2\] ibid |
