Skip to main content

Progressing the IANA functions into 2018

Davies iana services pti 750x425 08feb18 en

The last few years have been a period of intense focus on ICANN and the IANA functions — which are the management of key services including updating the DNS root zone, allocating global Internet Protocol address blocks to Regional Internet Registries, and assigning protocol parameters such as private enterprise numbers. With the U.S. government stepping away from its stewardship role over the IANA functions, and the Internet community coming together to form a replacement multistakeholder stewardship model, the priority within ICANN's team that performs these functions has stayed focused on stable and dependable service delivery.

Now, a little over a year after the transition of the stewardship of the IANA functions, we have a number of data points to reflect upon how we've performed. Most tangible of these measurements is our just completed annual customer survey, which we conducted for the sixth year. This year's results have provided clear indications that the IANA functions continue to be dependably delivered to high satisfaction levels. The results show accuracy should be our number one focus in delivering our service, with timeliness and processing quality ranking after that.

These survey outcomes echo the results we've seen in the comprehensive service level reporting we provide, with many community-defined metrics of performance reported either in real time, or through monthly reports. These metrics show consistent service delivery and a strong commitment to the community's defined service level targets.

Several new oversight mechanisms and committees were also established as a result of the transition of the stewardship to the multistakeholder community. The operation of those groups is stable and we've established a regular rhythm and methods of working together. We're working productively with many of these new organizations, including the Customer Standing Committee and the Root Zone Evolution Review Committee, as well as existing accountability measures such as those with the IAB and IETF leadership.

The community created a new ICANN legal affiliate called "Public Technical Identifiers" (PTI), which houses the IANA functions and the staff that deliver the services. PTI is now in its second year of operation. The PTI Board, including one new Director appointed through the ICANN Nominating Committee process, recently held a one-day workshop to discuss its oversight role.

On a more personal note, I have been a part of the IANA team since 2005, initially responsible for our root zone services and later leading our technical services. Since the start of this year, I have been entrusted to lead the whole team in the role of VP, IANA Services. Our team's remit remains to provide the dependable IANA service the community has come to expect, as well as implement a vision for modernizing and improving how we deliver these services to raise the bar moving forward. I am looking forward to meeting with many of you in the community in my new capacity and hearing your thoughts on our priorities and focus.

Our entire team is excited to continue to deliver reliable services to the whole Internet community, and we're looking forward to maintaining our productive partnerships with all of you in the Internet architectural and operations communities.

If you'll be attending ICANN61, I hope to see you there!


    bhabhikijawani  07:38 UTC on 15 February 2018

    thanx for sharing awesome and helpful post it helps me, and i have shared your to some of my big facebook groups, because your article deserve it.

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"""" is not an IDN."