Skip to main content
Resources

Contractual Compliance Monthly Update | November 2012

Table of Contents 1

Audit Program Update

On Monday, 26 November 2012, ICANN launched the Contractual Compliance Audit Program Pre-Audit Notification Phase. ICANN issued 323 Requests for Information (RFI) via email and fax to 317 Registrars and six top-level domains. During the RFI and Audit Phases, and as called for, ICANN will follow the contractual compliance 1-2-3 notification process with a turn-around time of 15 working days for first notice, five for second notice and five for third. Please note in table below that several additional days have been given between the 2nd and 3rd notice due to the holidays.

Audit Program Milestone Dates
Start End
Pre-Audit Notification Request for Info Audit Phase Reporting Phase Remediation
1st Notice 2nd
Notice 		3rd
Notice 		Begin End Begin End
13 Nov. 2012 26 Nov. 2012 17 Dec. 2012 28 Dec. 2012 7 Jan. 2013 12 Apr. 2013 15 April 2013 19 April 2013 22 April 2013

Reminder Note: The program will run on a three-year cycle during which each registry and registrar agreement will be randomly selected for audit over a three-year period.

The program consists of the six phases, the Planning Phase, Organizing Phase, Pre-Audit Notification Phase, Audit Phase, Reporting Phase and Remediation Phase.

Please refer to http://www.icann.org/en/resources/compliance/audits to learn more about this program.

Please refer to http://www.icann.org/en/resources/compliance/audits/faqs for the Frequently Asked Questions.

Please send your questions to ComplianceAudit@icann.org.

Below are statistics for 26 November 2012 thru 5 December 2012.

Number of Requests for Information Emails Sent (1st Notice)
  Sent Undeliverable Successful
Registrars 317 2 315
Registries 6 0 6
  323 2 321

*Note: The two that were undeliverable were sent to alternative email addresses.

 

Number of User Log-Ins to Audit Tool
  Assigned Logged In NOT Logged In
Registrars 317 72 245
Registries 6 1 5
  323 73 250

*Note: Many of the Registrars randomly selected fall into the family grouping, and hence; represent a large majority of the 'not logged in' data.

 

Number of Files Uploaded = 592
Over 600 emails received at ComplianceAudit@icann.org

 

60 Registrars and 5 Registries contacted ICANN.
The 65 above account for over 600 emails to ICANN.
Note: no open emails as of 5 December 2012.

Complaints Handling and Enforcement Summary

Complaints per Notification Cycle November 2012
Enforcement Activity for November 2012

Please refer to Contractual Compliance Notices for up-to-date information.

1 This update is provided for information purposes only. Please do not rely on the information contained within this update to make conclusions or business decisions.

A note about our terms of service:

We have updated our electronic terms of service to provide greater transparency and align with laws applicable to us. Learn more.

This site uses cookies to deliver an efficient user experience and to help us see how the site is used. Learn more.OK

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""icann.org"" is not an IDN."