Skip to main content

Building an Enhanced, Community Empowered ICANN

The submission of the IANA Stewardship Transition Package to the U.S. Government last month marked the end of an impressive proposal development effort by the global multistakeholder community. It also marked the beginning of the next, intense period of work, to ensure that the proposals can be implemented in a timely manner if they’re accepted.

We’ve seen significant progress since the submission, with a great deal of focus for ICANN and the community on updating ICANN’s Bylaws. The National Telecommunications and Information Administration (NTIA) has said they need to see adoption of any changes to ICANN’s Bylaws before they can complete their anticipated 90-day review. To meet this aggressive timeline, immediately following the ICANN55 meeting in Marrakech, a drafting team was formed consisting of ICANN’s legal team and the two external law firms involved with the Community Working Group (CWG-Stewardship) and Cross Community Working Group (CCWG-Accountability).  

The drafting team is working closely with representatives of all the involved community groups and the ICANN Board to ensure that the updated Bylaws accurately reflect the recommendations in the IANA Stewardship Transition Coordination Group (ICG) and the CCWG-Accountability proposals. Consistent with the current timeline, we will post the new draft Bylaws for a 30-day public comment period on 20 April 2016, with tentative adoption by 27 May. The Bylaws will only become effective upon the successful completion of the transition.

We are also continuing our joint planning efforts to remove NTIA’s administrative role from the root zone management system (outlined in my recent blog update), and as announced last week, ICANN and Verisign are currently undertaking a 90-day “parallel testing” period of the Root Zone Management System (RZMS). The parallel testing period is part of the proposal that ICANN and Verisign submitted to NTIA in August 2015.

Additionally, we hope to complete two other critical agreements this month – the Service Level Agreement with the five Regional Internet Registries (RIR) and the Memorandum of Understanding Supplemental Agreement with the Internet Engineering Task Force (IETF). We will make the drafts of these agreements available for a 30-day public review period prior to ICANN Board consideration.

To keep everyone informed on all these strands of planning, we will start publishing weekly updates on icann.org beginning next week. I encourage anyone who’s interested in the transition’s implementation details to check back for those updates.

There are 25 weeks left until the end of the current term of the IANA Functions contract with NTIA. We clearly have a lot of work to do as an organization and a community to be fully prepared, but the end goal of an enhanced, community empowered, independent ICANN, is well within sight.

Comments

    Nathalie Messie  13:44 UTC on 13 April 2016

    Hope you can finish in time we really need those changes.

    Fred Badina  08:18 UTC on 19 April 2016

    It's a really good initiative

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