ASO Review 2017
In 2017, the NRO engaged ITEMS International to conduct the second independent review of the ASO. The report, published in August 2017, outlined a set of 18 Recommendations, the first 17 of which the NRO resolved to accept and implement (see announcement).
The NRO also resolved to accept the 18th recommendation, “The NRO should initiate a public consultation, involving the five RIR communities, to determine the future structure of the ASO”, and has launched a community consultation on the issues identified in the ASO Review Report to facilitate this.
Details can be found in the ASO Review 2017 Community Consultations section.
ASO Review 2017: Recommendation Implementation Status
|Recommendation # 1: ICANN should consider updating its Bylaws to reflect the fact that the NRO will, like the GAC, and according to the ASO MoU, provide its own review mechanism for the review of ASO.||DEFERRED: This recommendation is a task that must be done jointly with ICANN and therefore should be taken up after the ASO Future Structure community consultation has been completed.|
|Recommendation # 2: The NRO should consider updating the ASO MoU to reflect the fact that the appropriate section of the New ICANN Bylaws regarding Organizational Reviews is Section 4.4 (previously Article IV, Section 4).||DEFERRED: This recommendation is a task that must be done jointly with ICANN and therefore should be taken up after the ASO Future Structure community consultation has been completed.|
|Recommendation # 3: The NRO should adopt a procedure for conducting periodic reviews of the ASO in line with processes used by the ICANN Organizational Effectiveness Committee.||IN PROGRESS.|
|Recommendation # 4: The signatories of the ASO MoU should consider updates to the MoU including i) the addition of AFRINIC as a signatory, ii) the removal of Appendix B. iii) updates in connection with the responsibilities of the ASO as a Decisional Participant in the ICANN Empowered Community.||DEFERRED: This recommendation is a task that must be done jointly with ICANN and therefore should be taken up after the ASO Future Structure community consultation has been completed.|
|Recommendation # 5: Upon completion of every independent review of the ASO, the NRO and ICANN should initiate discussions, as per Article 9 of the MoU, to examine results and consequences of their cooperation. The parties should determine if the ASO has a continuing purpose within the ICANN structure, and re-evaluate the MoU accordingly.||IN PROGRESS.|
|Recommendation # 6: The ASO AC should ensure that procedures are developed for Steps 12, 15 and 16 of the GPDP as described in Attachment A of the ASO MoU.||COMPLETED (February 2018): Global PDP Step #16 states that “Through the provisions of an agreement to be executed between the RIRs and ICANN, it is recognized that the ICANN Board has the ability to request that the ASO Address Council initiate a policy development process through the RIRs, using the policy development procedure described above.” While it is does reference “an agreement to be executed”, It is unclear if any additional procedure is actually necessary for ICANN to submit global policy proposals, since the the entire Global Policy development process itself is such a procedure; i.e. the ICANN Board can presently submit policy proposals to the ASO AC per the GPDP Step #1, just as any other party.|
|Recommendation # 7: The ASO should consider the adoption of a single, authoritative description of the GPDP for global numbering policies. The same description of the GPDP should appear in Attachment A of the ASO MoU and the relevant section of the Operating Procedures of the ASO AC (Currently Section 6).||IN PROGRESS.|
|Recommendation # 8: With a view to increasing awareness regarding the mission, main operations, and separation of roles between the ASO AC and the NRO EC within the ASO, the NRO should consider the use of more infographics on its website.||COMPLETED (July 2018): Infographics will be used on the website where possible.|
|Recommendation # 9: The ASO AC should implement term limits for the positions of Chair and Vice-Chair.||IN PROGRESS.|
|Recommendation # 10: The ASO AC should ensure that the duties of the Address Council Chair and the Address Council Vice-Chairs need to be added to the ASO AC Operating Procedures.||IN PROGRESS.|
|Recommendation # 11: The ASO AC should ensure that its internal procedure for the removal of an ICANN Board Director is consistent with Section 7.11 of the New ICANN Bylaws.||COMPLETED: The NRO EC is the decisional party unless the ASO AC decides to define procedures to enable it to participate in director removal.|
|Recommendation # 12: The ASO should establish the NRO Executive Secretary as the ASO Point of Contact (PoC). The ASO AC should establish procedures for forwarding communications to appropriate parties within the ASO.||COMPLETED (February 2018): The NRO agreed to review the contact points and procedures for reaching relevant parties in the ASO and NRO. The NRO did not, however, recommend proceeding with establishing the NRO Secretariat as the ASO contact point, but instead recommended reviewing and establishing clear contact points and procedures as appropriate. Contact pages on the ASO and NRO websites were subsequently updated.|
|Recommendation # 13: The ASO MoU should be updated to reflect the new reality of the Empowered Community and specify that the roles and responsibilities within the ASO must be clearly defined||COMPLETED (February 2018): The NRO believed that the Empowered Community is out of the scope of the ASO review, and that updating the MoU is not appropriate as the updates would be duplicative of information already contained in ICANN Bylaws.|
|Recommendation # 14: The ASO AC should either confirm that the designated representative of the ASO on the Empowered Community Administration will be the Chair of the NRO EC, or develop a procedure for appointing another representative.||COMPLETED (June 2018): The NRO confirmed that the NRO EC Secretary is the the ICANN Empowered Community Designated Representative of the ASO when it adopted the the ASO Procedures for Use of Empowered Community Powers.|
|Recommendation # 15: ASO AC meetings should be open to the public, except for discussions regarding the selection of individuals for ICANN roles.||IN PROGRESS.|
|Recommendation # 16: For its internal communications, and for most matters related to the operations of the ASO, the ASO should favour the use of a publicly archived mailing list. In exceptional circumstances, for issues (e.g. Board appointments) that cannot be discussed in public, a non-publicly archived list should be used||IN PROGRESS.|
|Recommendation # 17: In the interests of transparency, the ASO website should be updated with recent presentations, contact details and an archive of the activities of both the ASO AC and NRO EC.||IN PROGRESS.|
|Recommendation # 18: The NRO should initiate a public consultation, involving the five RIR communities, to determine the future structure of the ASO.||IN PROGRESS: Community Consultations are underway in the five RIR regions.|
Last modified on 26/10/2018