Go back

Adopted Resolutions - Special Meeting of the PTI Board | 21 September 2018

  1. Minutes of Prior Meeting
  2. PTI Point of Contact to IANA Naming Function Review

 

  1. Minutes of Prior Meeting

    Resolved (PTI2018.09.21.01) the minutes of the 24 June 2018 meeting are approved.

  2. PTI Point of Contact to IANA Naming Function Review

    Whereas, the ICANN Bylaws require "The [ICANN] Board, or an appropriate committee thereof, shall cause periodic and/or special reviews (each such review, an "IFR") of PTI's performance of the IANA naming function against the contractual requirements set forth in the IANA Naming Function Contract and the IANA Naming Function SOW to be carried out by an IANA Function Review Team ("IFRT") established in accordance with Article 18 of the ICANN Bylaws."

    Whereas, §18.2.a of the ICANN Bylaws requires that the first Periodic IFR shall be convened no later than 1 October 2018.

    Whereas, §18.8(e) of the ICANN Bylaws specifies that "[t]he PTI Board shall select a PTI staff member to serve as a point of contact to facilitate formal lines of communication between the IFRT and PTI."

    Resolved (PTI2018.09.21.02), the PTI Board hereby names PTI President Kim Davies to serve as the point of contact between PTI and the IFRT.

    Resolved (PTI2018.09.21.03), the PTI Board directs the PTI President to provide regular reporting to the PTI Board on the status of work on the IFRT.

    Rationale for Resolutions PTI2018.09.21.02 - 03:

    The ICANN Board convened the first periodic IANA Naming Function Review ("IFR") to satisfy the requirement under §18.2 of the ICANN Bylaws that the first periodic IFR be convened no later than 1 October 2018. The IFR is a new accountability mechanism created as part of the IANA stewardship transition to ensure that PTI meets the needs and expectations of its naming customers by adhering to the contractual requirements set forth in the IANA Naming Function Contract and the IANA Naming Function Statement of Work.

    In accordance with §18.8(e) of the ICANN Bylaws, the PTI Board has been directed to provide a staff member point of contact to support communication between the Review Team and PTI. While the PTI President will serve as point of contact to the IFRT, the PTI Board understands that due to the need for PTI to be involved with in supporting the IFRT to achieve a successful review, the PTI President may delegate some of the support work to other members of the PTI staff.

    This action is within PTI's mission as it supports PTI's performance of the IANA Functions, and is also meeting a requirement from the ICANN Bylaws on ICANN's mission relating to coordination of the allocation and assignment of names in the root zone, and directly supports the public interest.

A note about our terms of service:

We have updated our electronic terms of service to provide greater transparency and align with laws applicable to us. Learn more.

This site uses cookies to deliver an efficient user experience and to help us see how the site is used. Learn more.OK

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