Skip to main content

Final Implementation Update

In mid-August, ICANN submitted an Implementation Planning Status Report to the U.S. National Telecommunications and Information Administration (NTIA). The report provided a thorough inventory of the work that was accomplished by ICANN and the multistakeholder community to prepare for the IANA stewardship transition, and described the remaining tasks that will be completed before 30 September 2016 to allow the current term of the IANA functions contract to expire.

ICANN is pleased to confirm that all of the implementation tasks identified in the report are complete. Since issuance of the report on 12 August 2016, the remaining outstanding tasks have been finalized:

As a final step to removing NTIA’s role, NTIA and Verisign will amend the cooperative agreement between them. The Root Zone Maintainer Services Agreement between ICANN and Verisign will come into effect as soon as the cooperative agreement between Verisign and NTIA is amended, and until that time, ICANN and Verisign will continue to operate the current root zone management system processes.

With the completion of all required implementation tasks, the global multistakeholder community, with the support of ICANN the organization, is ready for the IANA stewardship transition to occur. We thank the ICANN community for their ongoing support and dedication throughout this transition process.

Comments

    ronald baione-doda  12:54 UTC on 01 October 2016

    The whistlebower process at ICANN is insufficient in my opinion until there is an explanation of that process provided to the public, no one has publicly explained what the whistleblower process is, how can you possibly transfer oversight of anything without first ensuring the entire process. Will websites like Wikileaks be the only public awareness method available? Human rights organizations should have been included as whistleblower contacts on a randomly selected monthly basis to provide another method for the multistakeholders within the post-transition process to alert the public to necessary information regarding nefarious external influences. Nice work by the media by the way, not a single article written about the current "3rd party phone call based ICANN whistleblower process", as was explained in a sentence or two to ICANN accountability participants, that should have been an obvious human rights issue. When Wikileaks or a similar website is reporting on undue influence on ICANN's multistakeholder post-transition process, I will have been proven correct in my arguments. The process of creating the framework for the proposal was not a bottom-up process, it was a top-down exclusionary agenda that harshly excluded new participants who simply wanted to discuss and learn about topics such as the ICANN whistleblower process. Public Archives: http://mm.icann.org/pipermail/accountability-cross-community/2015-November/008072.html http://mm.icann.org/pipermail/accountability-cross-community/2015-November/subject.html http://mm.icann.org/pipermail/accountability-cross-community/

    enginee khan mohammod kamruzzaman  07:20 UTC on 25 October 2016

    Thank you I have proud to good to know . "Todo"better together, Www.kmkamruzzaman.com Admin/Director Kmkamruzzaman

    A Hayward  17:15 UTC on 15 April 2017

    Money order

    A Hayward  18:17 UTC on 15 April 2017

    Money? Am I owed any?

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