Skip to main content

New ICANN Bylaws

Today, on behalf of the ICANN Board, I am pleased to announce the adoption of the new ICANN Bylaws, which reflect changes made as a result of the IANA Stewardship Transition package of proposals. The new Bylaws are the result of hundreds of hours of work by the community and the legal teams. The Regional Internet Registries Service Level Agreement and Internet Engineering Task Force Memorandum of Understanding Supplemental Agreement have also been approved for signing and will go into effect after the transition.

Later today, ICANN will be transmitting the new Bylaws to the U.S. Department of Commerce’s National Telecommunications and Information Administration (NTIA). NTIA has previously stated that adoption of the new Bylaws is required for them to complete their review of the proposals, which is expected to occur in June.

This is an important milestone for ICANN and the community. As we await the release of NTIA’s report, we continue to prepare for implementation of the transition proposals. We thank everyone for their continued hard work and support during this transition process.


    Constantine Roussos  13:52 UTC on 27 May 2016

    Dear Chairman Dr. Crocker, DotMusic commends the community for all their work. DotMusic has submitted numerous public comments during the public comment period ( relating to the draft new ICANN Bylaws to increase ICANN's transparency and accountability (See DotMusic public comments at ICANN staff created a report on the public comments (See but did not indicate why some revisions were accepted while others that ensured ICANN increased its accountability and transparency were not. It is clear that the ICANN Board hurried to accept the new Bylaws. 6 days is not reasonable time to assess and adequately take into consideration over 30 public comments, some of which were quite detailed. Moreover, there was no clarification or discussion by Staff or the Board why some public comments to increase ICANN's accountability and transparency were not adopted. While ICANN takes on the position of multi-stakeholder bottom up decision-making, it means nothing if comments by certain organizations are always shunned, ignored and dismissed at the gain of certain special interests or to provide ICANN wiggle room to escape true accountability and transparency during the Independent Review Process or Reconsideration Request process. Certain aspects of the new Bylaws pertaining to accountability mechanisms remain problematic and once again are riddled with the appearance of conflicts of interest in favor of ICANN. The new ICANN Bylaws urgently require significantly more responsible, meaningful and impactful revisions to hold ICANN accountable and increase transparency. In fact, internet users and public interest demand it. Thus far, the Internet community has been ineffective in holding ICANN accountable and transparent. It appears this will continue. Constantine Roussos DotMusic

    John Caswell  20:36 UTC on 18 April 2017

    The other set of recommendations related to enhancing ICANN Accountability in relation to the IANA Stewardship Transition.

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