Skip to main content

Enhancing Transparency in Contractual Compliance Reporting

In Jamie Hedlund’s blog, Six weeks in Contractual Compliance and Consumer Safeguards, he briefed the community on three department initiatives (facilitate community-wide consumer safeguard discussion; boost DNS abuse mitigation efforts; and enhance transparency around contractual compliance). In this blog, I want to provide you an update on the increased transparency initiative around compliance reporting.

Over the past several months we enhanced the ICANN Contractual Compliance Performance Reports in a variety of ways, including:

  • Enhanced Monthly Reporting - we added information on the subject matter of complaints in the compliance monthly dashboard based on recommendations from the Competition, Consumer Choice, and Consumer Trust Review Team draft report and the Governmental Advisory Committee’s Copenhagen Communique. A few examples include:
    1. Report the WHOIS Inaccuracy complaint by three categories – syntax, operability, and identity.
    2. Report on the subject of registrar related Domain Name System (DNS) abuse complaints such as spam, pharming, phishing, malware, and botnets in addition to counterfeiting, pharmaceutical, fraudulent and deceptive practices, trademark or copyright infringement, and registrar abuse contact.
  • New Quarterly Reports - our quarterly reports are intended to replace the metrics provided at the Annual General Meeting and the Community Forum during the Compliance Program Update session. This will bring a regular cadence to reporting and eliminate the nearly six-month gap due to the Policy Forum at which no reporting is provided.
  • New Annual Reports – our new annual reports are intended to provide a calendar year view into the compliance landscape. A few examples include:
    1. Report the registrar and registry complaint types by legacy gTLDs and new gTLDs.
    2. Report the enforcement reasons for registrars and registries.
  • Increased transparency around complaints in anticipation of future policy requests to measure the effectiveness of the new Transfer Policy. We added additional metrics on the subject matter of ICANN received complaints, which will be relevant for policy review and evaluation.

Additional work is underway to provide a greater detail of reporting on complaints related to safeguards and Public Interest Commitments. All current and past Contractual Compliance Performance Reports are available on ICANN.org

Thank you for your recommendations and requests to enhance transparency in contractual compliance. We welcome your feedback as we continue to improve our reporting. if you have any questions, please contact ICANN Contractual Compliance at compliance@icann.org.

Comments

    ShikhaSharma  01:22 UTC on 23 October 2017

    Packers And Movers Jaipur is recognized as a business manager providing wide-ranging and differentiate service appearance as well as Relocation Shifting, Logistics and Transportation, Facilities managing, strategy & Designing services. jaipurpackersandmovers

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."