Skip to main content

ICANN Submits Implementation Planning Status Report to NTIA

ICANN today submitted an implementation planning status report [PDF, 339 KB] to the National Telecommunications and Information Administration (NTIA), in response to a request [PDF, 68 KB] NTIA made on 9 June 2016.

ICANN and the various stakeholder groups have worked tirelessly to complete the tasks specified by NTIA and the global multistakeholder community.

The following implementation tasks are complete:

  • On May 27, 2016, the ICANN Board approved the revisions to the ICANN Bylaws.

  • On June 24, 2016, ICANN signed the 2016 Supplemental Agreement with the Internet Engineering Taskforce (IETF).

  • On June 29, 2016, ICANN signed the Service Level Agreement (SLA) with the five Regional Internet Registries (RIRs).

  • On July 5, 2016, ICANN and Verisign successfully completed the 90-day parallel testing period on the Root Zone Management System.

  • On August 9, 2016, the ICANN Board approved the amendments to the ICANN Articles of Incorporation.

  • On August 10, 2016, the membership of the Customer Standing Committee (CSC) was approved.

  • On August 10, 2016, the Incorporation Documents for the "Post-Transition IANA" organization were filed and received by the California Secretary of State, under the name Public Technical Identifiers (which will be more commonly referred to as PTI).

  • On August 12, 2016, the Root Zone Evolution Review Committee (RZERC) was formed.

Significant progress has been made on the following implementation tasks, which will be complete in advance of September 30, 2016:

  • On August 18, 2016, the final PTI Bylaws will be published. These will incorporate comments received through the ICANN public comment process, which ran from July 12, 2016 to August 11, 2016. Once published, the PTI Bylaws will be ready for ICANN and PTI Board approval.

  • On September 16, 2016, the ICANN-PTI Naming Function Agreement will be published. It is undergoing a 30-day ICANN public comment process, which will close on September 9, 2016. The final Agreement will be published on September 16, 2016. Once published, the Agreement will be ready for ICANN and PTI Board approval and signature.

    • The customer service complaint and escalation mechanisms defined by the domain names community were incorporated into the Naming Function Agreement.

  • On September 16, 2016, the ICANN-PTI Services Agreement will be published. It is currently being reviewed and discussed with the community. Once published, the Agreement will be ready for ICANN and PTI Board approval and signature.

  • Several agreements and documents are complete and ready for signature or Board approval, which will be complete in advance of September 20, 2016:

    • On August 2, 2016, the ICANN-PTI Protocol Parameter Subcontracting Agreement was completed and is ready for ICANN and PTI signature.

    • On August 9, 2016, the ICANN Board approved the Root Zone Maintainer Agreement. ICANN, Verisign, and NTIA will coordinate a date to sign it.

    • On August 11, 2016, the Service Level Expectations (SLEs) for the domain names community were completed and are ready for incorporation into the final Naming Function Agreement. The Naming Function Agreement requires ICANN and PTI Board approval.

    • On August 11, 2016 the ICANN-PTI Numbers Subcontracting Agreement was completed and is ready for ICANN and PTI signature.

    • On August 12, 2016, the PTI governance documents, including the conflict of interest policy, Board code of conduct and expected standards of behavior were completed after an ICANN public comment process and are ready for PTI Board adoption.

ICANN, working with the multistakeholder community, confirms that all required IANA functions stewardship transition tasks specified in NTIA's June 9, 2016 letter are complete, and all other tasks in support of the IANA stewardship transition are either in a final review stage or awaiting approval, which will be complete in advance of September 30, 2016 to allow the IANA functions contract to expire.

Review the IANA Stewardship Transition Proposal Implementation Planning Status Report for more information: https://www.icann.org/en/system/files/files/iana-stewardship-implementation-planning-status-12aug16-en.pdf [PDF, 932 KB].


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