Skip to main content

ATRT2 Implementation Program Update

We are pleased to provide the first update on the implementation of recommendations from the Second Accountability and Transparency Review Team (ATRT2). ICANN has kicked off the implementation work, following methodology rooted in project management industry standards. ICANN community can track status and progress of implementation work on the ATRT2 Program Implementation Wiki through Implementation Executive Summaries. Updates will be provided each trimester through multiple communication channels and at ICANN meetings, beginning with ICANN51 in Los Angeles. A public session, ATRT2 Implementation Update will take place on Wednesday, 15 October 2014; 14:00 to 15:15 PDT.

The implementation of recommendations [PDF, 3.45 MB] from the Second Accountability and Transparency Review Team (ATRT2) began in June 2014, as soon as ICANN's Board of Directors accepted the recommendations through resolution directing ICANN to begin the work.

As background, the review was conducted by "16 ATRT2 members, who were drawn from the ICANN community via a public notice as well as recommendations from ICANN's SOs and ACs, and selected by the chairs of the ICANN Board and its Governmental Advisory Committee. These community members spent nearly a year reviewing, studying, questioning, debating and listening to the community as well as staff in preparing their report."1 Final report was published on December 31, 2013 and included 12 recommendations within the following areas:

Areas Recommendations
Board Performance & Work Practices ## 1-2-3
Policy/Implementation/Executive Function #4
Decision Making Transparency & Appeals ## 5, 7, 9
GAC Operations & Interaction #6
Multilingualism #8
Cross-Community Deliberation #10
AoC Review Process Effectiveness #11
Financial Accountability & Transparency #12

Implementation Methodology – Project Management Discipline

ICANN worked closely with the ATRT2 throughout 2013, laying down a foundation to ensure the implementation of the recommendations would be timely and effective. An implementation methodology was designed based on the global standards of The Project Management Institute - rules, guidelines, and characteristics for the project and development of a management portfolio. The PMI standards are widely accepted with a goal towards achieving professional excellence. Benefits include a clear scope definition, company-wide resource planning, monitoring against timelines and consistent reporting.

ICANN's commitment to accountability and transparency, in the interest of Internet users globally, was formalized and documented in 2009 in the Affirmation of Commitments (AoC) agreement with the U.S. Government. It set a course for ongoing evolution and improvement in ICANN's accountability. ICANN views the implementation methodology it chose as the means of ensuring an organization-wide commitment to continuous improvement. The method of implementing the ATRT2's recommendations will serve as a pilot. ICANN will refine the approach to apply consistently to AoC and other review efforts.

ATRT Implementation Methodology

Roles and Responsibilities

The 12 ATRT2 recommendations contain 51 components. A dedicated Project Manager is responsible for facilitating planning, monitoring progress, conducting risk assessments and providing ongoing reporting across multiple ICANN teams. Each recommendation is assigned a project sponsor and an owner responsible for planning and executing the necessary implementation steps, securing resources and tracking performance via Key Success Factors and Key Performance Indicators. An Advisory Committee consisting of several members of ICANN'S Executive Leadership team has been appointed to oversee the implementation work and ensure timely, clear and relevant reporting to ICANN Stakeholders.

Progress Reporting

With the experience of two previous Accountability and Transparency reviews, ICANN understands the importance of timely and effective communications. In fact, one of the ATRT2 recommendations specifically addresses implementation reporting. Updates on the progress of implementing the recommendations will be posted and reported each trimester through multiple communication channels and at ICANN meetings, beginning with ICANN51 in Los Angeles. A public session, ATRT2 Implementation Update will take place on Wednesday, 15 October 2014; 14:00 to 15:15 PDT.

Additionally, webinars on implementation progress will be offered periodically to provide ICANN stakeholders an opportunity to ask questions and offer feedback.

At this time, projects implementing all 12 ATRT2 recommendations have been initiated with several teams executing their initial implementation steps. With 51 distinct recommendation components to develop, the timeframe for implementation will vary depending on the complexity of the recommendation and its key dependencies. For example, synchronization and alignment will likely take place in conjunction with the work underway to Enhance ICANN Accountability Process. Such dependencies and connections will be addressed in the Implementation Summaries provided for each recommendation on the ATRT2 Implementation Program wiki.

Each project will be tracked in ICANN's Portfolio Management System – stakeholders, Board and staff can see the progress on ICANN's web site.

Additional information

Description Link
Board Resolution (2014.06.26.14 – 2014.06.26.15) accepting recommendations and directing implementation https://www.icann.org/resources/board-material/resolutions-2014-06-26-en#2.d
Final Report of the Second Accountability and Transparency Review Team https://www.icann.org/en/about/aoc-review/atrt/final-recommendations-31dec13-en.pdf [PDF, 3.45 MB]
ATRT2 wiki – review workspace https://community.icann.org/pages/viewpage.action?pageId=40176025
ATRT2 Implementation Program wiki https://community.icann.org/display/prgrmatrt2impl/ATRT2+Implementation+Program+Home

1 How ICANN is Accountable to the Global Community, by Fadi Chehadé on February 12, 2014


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