Skip to main content

Implementation Planning, Execution, and NTIA’s Response

In order to fulfill the tasks assigned by NTIA and the community-developed proposals for the IANA stewardship transition, ICANN and the multistakeholder community have dedicated significant time and resources over the past eight months developing plans for implementation. The ICANN community and staff continue to work hard to ensure that all necessary tasks are completed and the proposals can be implemented in a timely manner in advance of 30 September 2016 to allow the IANA functions contract to expire.

On 9 June 2016, NTIA requested that ICANN submit an implementation planning status report by 12 August 2016. Last Friday, ICANN submitted a report to NTIA that stated: “All required tasks specified in NTIA’s 9 June 2016 letter are complete, and all other tasks in support of the transition are either in a final review stage or awaiting approval, which will be complete in advance of 30 September 2016 to allow the IANA functions contract to expire.”

In a letter to ICANN today, NTIA stated, “NTIA has thoroughly reviewed the report. Based on that review, barring any significant impediment, NTIA intends to allow the IANA functions contract to expire as of October 1.”

ICANN is pleased with NTIA’s statement and is focused on the remaining tasks to be completed by 30 September 2016:

  • Finalize the PTI Bylaws: ICANN is currently incorporating comments received during the public comment process that ran from 12 July-11 August and will post a final version on 18 August.
  • Finalize the ICANN-PTI Naming Function Agreement, which includes the customer service complaint and escalation mechanisms defined by the CWG-Stewardship: This Agreement is currently out for public comment until 9 September 2016, and a final version will be posted on 16 September 2016.
  • Finalize the ICANN-PTI Services Agreement: The Agreement is currently being reviewed and discussed with the multistakeholder community, and a final version will be posted on 16 September 2016.

In addition, there are four agreements and documents that have been finalized and require signatures, or ICANN Board and/or PTI Board approval before they can be considered complete:

  • The Root Zone Maintainer Agreement.
  • The ICANN-PTI Protocol Parameters Subcontracting Agreement.
  • The ICANN-PTI Numbers Subcontracting Agreement.
  • The PTI Conflict of Interest Policy, Board Code of Conduct, and Expected Standards of Behavior.

I encourage anyone who is interested in the details of both the completed and ongoing implementation tasks to read ICANN’s 31-page implementation planning status report. ICANN is confident that everything will be implemented in advance of 30 September 2016 to allow the IANA functions contract to expire. The global multistakeholder community, with the support of ICANN the organization, is ready for the IANA stewardship transition to occur.

Comments

    Marie Vaskez  02:56 UTC on 26 August 2016

    Good to know all this

    Kaecla Raedka  04:42 UTC on 08 September 2016

    This is a very useful post and I have found good information here and I really appreciate the efforts of the writer of this essay for sharing nice ideas. Thanks!

    Michelle Clunie  03:38 UTC on 09 November 2016

    Looking forward for implements that ICANN is deploying will impact positively confident that everything will be implemented with the support of ICANN the organization, is ready for the IANA

    tarry yon  05:29 UTC on 20 December 2016

    In addition, there are four agreements and documents that have been finalized and require signatures, or ICANN Board and/or PTI Board approval http://uspstrackingservice.com before they can be considered complete Delete Comment

    Word Cookies Game Answers  20:03 UTC on 21 March 2017

    I would like to say that this blog really convinced me to do it! Thanks, very good post.

    Dang Thanh Tung  12:11 UTC on 03 April 2017

    Great information! Thanks for nice post.

    Dao My Linh  01:22 UTC on 12 April 2017

    How interesting this post is! Thanks so much for the useful information you mentioned. Hope that ICANN can be fully deployed and brings the impressive effects.

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