Skip to main content

WHOIS Review Team

Open: 4 March 2011
Closed: 17 April 2011


The WHOIS Policy Review Team was launched in October 2010 in line with the Affirmation of Commitments (AoC) provisions, section 9.3.1, which stipulates that:

"ICANN additionally commits to enforcing its existing policy relating to WHOIS, subject to applicable laws. Such existing policy requires that ICANN implement measures to maintain timely, unrestricted and public access to accurate and complete WHOIS information, including registrant, technical, billing, and administrative contact information. One year from the effective date of this document and then no less frequently than every three years thereafter, ICANN will organize a review of WHOIS policy and its implementation to assess the extent to which WHOIS policy is effective and its implementation meets the legitimate needs of law enforcement and promotes consumer trust."

The WHOIS Review Team would welcome public comment on the following issues:

  1. Scope of Work and Roadmap

  2. Outreach Plan

  3. Action Plan

  4. List of Key Definitions

    1. Law Enforcement:
      Law Enforcement shall be considered to be an entity authorized by a government and whose responsibilities include the maintenance, co-ordination, or enforcement of laws, multi-national treaty or government-imposed legal obligations.

    2. Applicable Laws:
      Includes any and all local and national laws that regulate and/or control the collection, use, access, and disclosure of personally identifiable information. It may also include other relevant legal obligations, including U.N. Universal Declaration of Human Rights and the U.N. Guidelines for the Regulation of Computerized Personal Data Files.

    3. Producers and Maintainers of WHOIS Data:

      1. Producers: The individuals or organizations supplying contact data for inclusion into WHOIS data.

      2. Maintainers: The WHOIS Review Team proposes to subdivide this category in to:

        • Data Controllers: Individuals or organizations that define the data to be collected, require its release, and govern its use. May or may not be directly involved in these functions.

        • Data Processors: Individuals or organizations engaged in the collection, storage, and release of data, according to the terms defined by the Data Controller. They do -not- determine the nature or use of the data that they collect or maintain.

    4. Consumer:

      What is a "consumer"?

      There is no single universally agreed definition of 'consumer', and legal definitions in different jurisdictions vary widely. Some are narrow and limited to 'natural persons', while others are broader and include various types of organisations.

      The WHOIS review team has been considering a broad interpretation of the term 'consumer', as this would allow a broad range of perspectives to be considered by the review team. This appears to be consistent with the intention of the drafters of the AoC.

      In the global sense, "consumer" may mean:

      • All Internet users including natural persons, commercial and non-commercial entities, government and academic entities.

      And specifically within the context of this review, a "consumer" w.r.t. WHOIS data and WHOIS Service may mean:

      • Any consumer that acts as a Producer of WHOIS data (see above), Maintainer of WHOIS data and provider of WHOIS Service (e.g. Registrars), or User of WHOIS data (e.g. – individuals, commercial or non-commercial entities who legitimately query the WHOIS data).

      Feedback request from community

      Community feedback is desired on the WHOIS Review Team's approach to this definition. Is it too broad or too restrictive? In either case, how should it be changed?

The WHOIS Review Team also welcomes general comments on the above issues, and any other issues, which the community would like the RT to consider at this early stage in their work.

The public comment will remain open for 45 days and close on 17 April 2011.

To find minutes of our meetings as well as documents and work in progress, please check our public community wiki at:

Staff member responsible: Olof Nordling

Announcement | Comments | Summary/analysis of comments

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