AT-LARGE GATEWAY

At-Large Website

ALAC

RALOs

At-Large Regional Policy Engagement Program (ARPEP)

At-Large Governance

At-Large Reports

Policy Comments & Advice

Working Groups

ICANN Meetings

At-Large Summit (ATLAS III)

At-Large Review Implementation Plan Development

ALAC and RALO Elections, Selections, and Appointments

At-Large Priority Activities - 2021

Public Comment CloseStatement
Name 

Status

Assignee(s)

Call for
Comments Open		Call for
Comments
Close 		Vote OpenVote CloseDate of SubmissionStaff Contact and EmailStatement Number


02 February 2018


Operating Standards for ICANN's Specific Reviews


No Statement









Lars Hoffmann
lars.hoffmann@icann.org


Hide the information below, please click here 


Brief Overview

Purpose: The purpose of this public comment is to solicit feedback on:

  1. The underlying principles that are reflected in the draft Operating Standards [PDF, 303 KB], especially: for the community to agree on the review scope prior to the review team being selected; to assure selected review teams have the necessary skill set and diversity to conduct a successful review.
  2. The specific proposals and content that are contained in the draft Operating Standards[PDF, 303 KB], including but not limited to the proposal on scope setting and review team selection.

Current Status:

The current draft has been compiled by ICANN's Multistakeholder Strategy and Strategic Initiatives team, with community input solicited throughout ICANN57, ICANN58, and a webinar in February 2017. Most procedures detailed in the draft Operating Standards [PDF, 303 KB] are either based on existing best practices, or on processes that have been adapted from comparable procedures already in existence elsewhere within ICANN.

Next Steps: This extended public comment will remain open for 90 days. Concurrently, a webinar will be held on Thursday, 19 October, and a cross-community session on the Operating Standards is scheduled for ICANN60. Input received from this public comment, and all other feedback received through the aforementioned webinar and cross-community session will inform the next steps.

Section I: Description and Explanation

The Operating Standards are subject to the relevant provisions in the ICANN Bylaws, see Article IV, Section 4.6. Their purpose is to provide for a transparent and consistent review process by documenting rules and procedures. Please note, most procedures detailed in the draft Operating Standards [PDF, 303 KB] are either based on existing best practices, or on processes that have been adapted from comparable procedures already in existence elsewhere within ICANN.

The draft Operating Standards [PDF, 303 KB] address, among other things:

  • Scope setting for specific reviews
  • Review team selection
  • Roles and responsibilities of Review Team members
  • Review team working methods
  • Use of independent experts
  • Review output
  • Amending the Operating Standards

Section II: Background

The purpose of Operating Standards, once adopted, is to provide consistency, clarity, and transparency around ICANN's four specific reviews: Competition, Consumer Trust and Consumer Choice Review, the Security, Stability, and Resiliency of the DNS Review, the Accountability and Transparency Review, and the Registration Directory Service Review.

ICANN Bylaws call for Operating Standards for Specific Reviews that "shall be developed through community consultation" (Section 4.6). To facilitate and promote community consultation on the Operating Standards, the ICANN organization held sessions for community input during ICANN57, ICANN58, and organized a webinar in February 2017.

Section III: Relevant Resources



Section IV: Additional Information

Section V: Reports

Staff Contact

Lars Hoffmann
lars.hoffmann@icann.org

FINAL VERSION TO BE SUBMITTED IF RATIFIED

The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote. 


 

FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.


 

FIRST DRAFT SUBMITTED

The first draft submitted will be placed here before the call for comments begins.


3 Comments

  1. Ariel Liang

    Comment from Carlton Samuels

    ==

    Having participated in 2 RTs to date, I see no more than what is standard practice codified.  All the important parts are there. Not sure it requires more than a tick mark comment.

    Other than that, did anyone notice in the description of skills relevant for RT members to participate and in the case of those for the RDS team, only "familiarity" is required? Compared to others where the verbs tend to be "Experience", "Understanding" and "Knowledge"! 

    Makes for a fella with an inquiring mind to go hmmmmmm.

  2. Ariel Liang

    Comment from Jabhera Matogoro

    ==

    It is very important for ALAC to provide its comments and input on this process. I was appointed to represent ALAC to the first ICANN Specific Review (ICANN SSR2 RT) after IANA Transition. The lack of this Operational Standard it has resulted to "pause" cuased by ICANN Board.

    While the "pause" provide a critical input to the review process but without a clear and/or good operational standard then there is a number of challenges and would like our input to be submitted for the same.

  3. Dev Anand Teelucksingh

    Just an observation that ICANN should have some capacity training/teaching resources to aid the wider SO/AC community better understand what is expected in a review team and to learn the core skills needed by review team members.

    This would help volunteers from the SO/AC community be better able to participate in future reviews and in turn ensure future reviews are conducted in a transparent, consistent, efficient, and predictable manner.