Skip to main content

IANA Stewardship Transition Implementation Planning: Taking Stock of the Last Two Months and Looking Forward to 2016

The last update I provided was just over two months ago as we were heading into ICANN54 in Dublin. Our goal at that time was to receive feedback and better understand the community’s need for reporting and oversight of implementation planning for the IANA Stewardship Transition. In looking back at our progress since October, we achieved this and much more.

We are now providing monthly status updates on implementation planning efforts to the leadership teams of the CCWG-Accountability, CWG-Stewardship, CRISP Team, IANAPLAN WG, GNSO, ccNSO, IETF, IAB, and RIRs on the Transition Program Facilitation Management calls. Additionally, we have established a reporting cadence with the CWG-Stewardship by providing more detailed implementation planning status updates on the group’s bi-weekly calls. We are also working with all of the operational communities on defining service levels and documenting our relationships with them, as well as on the IANA Intellectual Property Rights. On the CCWG-Accountability side, we look forward to engaging with the group once its Work Stream 1 Recommendations are finalized.

Shortly after ICANN54, we launched a dedicated web page to provide the community with updates on implementation planning activities. We have been building out this web page to provide a more seamless browsing experience, including sort and filter capabilities. Be on the look out for more on this in the coming weeks.

On the U.S. Government side, we have been engaging with NTIA on our planning efforts. The feedback from NTIA has been very helpful in developing our plans and overall timelines to allow ICANN to plan for implementing as early as possible while respecting the current IANA Functions Contract. 

In my pre-ICANN54 blog, I wrote that our assessment showed that we would need four months to complete the IANA Stewardship Transition implementation, assuming the proposals are approved. This timetable has not changed. However, we hope that our continued collaboration with the community, engagement with NTIA, and careful project planning will enable us to complete the necessary implementation as efficiently as possible to meet a conclusion in time for a transition in 2016. We will continue to monitor progress, and regularly report back to the community.

As we head into 2016, our team looks forward to further collaboration with the community toward a successful and on-time transition. 

Happy holidays to those celebrating this season and best wishes into the New Year! 


    Johan  15:24 UTC on 26 December 2015

    Thank you for these changes in the platform that will only improve the experience of your users. Many web actors should follow your example. Happy holidays to all your team.

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