Skip to main content

Review Procedure to Handle Policy Proposals Submitted by the ASO Address Council in Line with the ASO MoU

Deadline for comments extended to 27 June


According to the ASO MoU, in Section 5 Global Policy Development Process, ICANN agreed to the following:

Under this agreement the ICANN Board will ratify proposed global policies in accordance with the Global Policy Development Process, using review procedures as determined by ICANN. ICANN will publish these procedures no later than ninety (90) days from the date of the signature of this agreement by all parties.

The MoU, available on: was signed on 21 October 2004, meaning that the agreed publishing was late, taking place on 6 April 2005.

The public comment period ended 9 May 2005. By then, comments from four parties had been submitted. These comments have been analyzed and considered in the following updated version of the procedure, which is posted for a second round of public comments.

Proposed review procedure steps

  1. The ASO Address Council sends the proposed policy to the ICANN Board Secretary who formally shall acknowledge receipt of the proposal within one business day. In case the proposal is formally incomplete, the Board Secretary may refer it back to the ASO Address Council for completion, otherwise the 60-day window for Board response to the ASO Address Council starts and the review procedure outlined hereafter commences.
  2. The Board, acting through the President, assigns the activities foreseen in the MoU, Attachment A, article 8, (stating that "The ICANN Board may review the policy proposal and may ask questions and otherwise consult with the ASO Address Council and/or the RIRs acting collectively through the NRO. The ICANN Board may also consult with other parties as the Board considers appropriate.") to ICANN staff.
  3. If deemed appropriate by ICANN staff so assigned in line with 2 above, external consultancy assistance may be called upon to assist in the review process.
  4. The proposal shall be posted for public comments within 5 business days, with comments due within 21 days from posting. All ICANN Supporting Organizations and Advisory Committees shall be immediately notified of the posting and their comments invited as appropriate.
  5. During all the steps 1-4 above, ICANN staff so assigned, may ask the ASO Address Council for clarifications of the proposal, as appropriate. Such questions for clarifications shall be reasonable, concise and bundled. The ASO Address Council shall respond to such questions within 10 business days.
  6. ICANN staff analyzes comments received following step 2, as well as prior comments put forward during the ASO PDP, and compiles within 10 business days from the end of the comment period a Staff Recommendation which is forwarded to the Board for consideration. The Staff Recommendation shall contain reasoned opinions on all material issues and motivations for proposed decisions.
  7. The Board takes its decision on the proposal and informs the ASO Address Council thereof, in line with the MoU provisions in Attachment A, articles 9-11. Relevant MoU provisions in Attachment A, articles 10-15, apply, should the Board request changes to the proposal or reject it.
  8. As part of the decision of the Board, the Board shall, as appropriate, give authorization or direction to the ICANN staff to take all necessary steps to implement the policy. Should the Board fail to take action as defined by the MoU provisions in Attachment A, article 10, within the 60-day window, the policy is deemed to be accepted by the Board and it becomes global policy.
  9. Throughout the Review Procedure, from policy proposal to the outcome of the review, ICANN will maintain on the Website, a status web page detailing the progress. This web page shall describe the initial proposal for a policy, all discussions and comments submitted in the process, all reports and recommendations produced on the matter and the outcome of the review.

Please submit your comments by 27 June 2005.

Click here to submit comments on the Proposed Review Procedure for ASO Policy Proposals

Click here to view comments on the Proposed Review Procedure for ASO Policy Proposals

More Announcements
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as"""" is not an IDN."